Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • spec
  • lib
  • gitlab
  • omniauth_initializer_spec.rb
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Bump omniauth_openid_connect to 0.3.1 · 350f19f5
    Stan Hu authored Jun 08, 2019
    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.
    350f19f5
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7