Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9396

Closed
Open
Created Jun 17, 2015 by Administrator@rootOwner

OAuth Login does not redirect to authorization page

Created by: ClassicCut

When using gitlab as an oauth application provider, if I'm prompted to sign-in to gitlab as part of the authorization flow, I am redirected to the home page, rather than the authorize application page, thus kicking me out of the oauth authorization flow.

To reproduce: create an oauth application on gitlab. On an external service configured to use gitlab as an oauth provider, initiate an oauth session (when not currently signed-in to gitlab)

Expected behavior: after logging in, I should be redirected to the authorize application page, prompting me to authorize the requesting application.

Observed behavior: after logging in to gitlab, the oauth flow breaks, and I'm dumped into the gitlab home page/dashboard.

If I'm already logged in to gitlab, the whole oauth authorization flow works as expected.

*edit: I'm experiencing this on both gitlab.com (version 7.12.0-ee) and a private hosted gitlab instance (version 7.11.2)

Assignee
Assign to
Time tracking