diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-06-08 07:12:47 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-06-08 08:04:44 -0700 |
| commit | 350f19f59fd1e44c18699cc46cfff71a92d7e0a4 (patch) | |
| tree | b4aa7849dc1e297493589ee2739f490ba9fd751a /Gemfile.lock | |
| parent | 2a01cb79560a861a7e32e9ee11e823f22e181aa1 (diff) | |
| download | gitlab-ce-350f19f59fd1e44c18699cc46cfff71a92d7e0a4.tar.gz | |
Bump omniauth_openid_connect to 0.3.1sh-update-openid-omniauth-gem
In https://gitlab.com/gitlab-org/gitlab-ce/issues/62208, users were
seeing 404 errors when they configured their OpenID provider without a
name parameter since OmniAuth would use the name `openidconnect` instead
`openid_connect`.
https://github.com/m0n9oose/omniauth_openid_connect/pull/23 makes the
default parameter `openid_connect` so this additional initializer in
GitLab is not necessary. Plus, this change enables users to use multiple
OpenID Connect providers if they desire.
Diffstat (limited to 'Gemfile.lock')
| -rw-r--r-- | Gemfile.lock | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Gemfile.lock b/Gemfile.lock index 785a77bc202..92ffbcc6ab7 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -587,7 +587,7 @@ GEM activesupport nokogiri (>= 1.4.4) omniauth (~> 1.0) - omniauth_openid_connect (0.3.0) + omniauth_openid_connect (0.3.1) addressable (~> 2.5) omniauth (~> 1.3) openid_connect (~> 1.1) @@ -1159,7 +1159,7 @@ DEPENDENCIES omniauth-twitter (~> 1.4) omniauth-ultraauth (~> 0.0.2) omniauth_crowd (~> 2.2.0) - omniauth_openid_connect (~> 0.3.0) + omniauth_openid_connect (~> 0.3.1) org-ruby (~> 0.9.12) peek (~> 1.0.1) peek-gc (~> 0.0.2) |