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
  • doc
  • integration
  • github.md
Find file BlameHistoryPermalink
  • Eric K Idema's avatar
    Fix documentation for Github integration authorization callback url. · e921fc90
    Eric K Idema authored May 10, 2016
    There are two callbacks that could be used with Github integration:
    
      * /import/github/callback (used by project import)
      * /users/auth/github/callback (used by OmniAuth)
    
    Github's documentation suggests that authorization callback url should be
    set to the longest common path.
    
    https://developer.github.com/v3/oauth/#redirect-urls
    
    Configuring according to the previous documentation resulted in a
    redirect_uri_mismatch error from Github when logging in via OmniAuth.
    e921fc90
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7