Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #9411 authenticate with GitHub
Actions
Summary
user
authenticate with GitHub
Empty

This is a follow up to story #8631 since we broke GitHub by fixing our implementation to follow stricly OpenID Connect specification. The initial acceptance criteria must be respected.

  • Administrators can configure the GitHub authentication plugin in the same area than the OpenID Connect providers.
  • Administrators only have to provide a client ID and secret.
  • Login button is displayed in the same area than the others OpenID Connect login buttons.
Empty
Empty
Status
Empty
Canceled
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
You can find description of the web application flow for GitHub here: https://developer.github.com/v3/oauth/#web-application-flow

The description of the user info endpoint can be found here: https://developer.github.com/v3/users/
Details
#9411
Thomas Gerbet (tgerbet)
2018-07-17 11:26
2016-08-22 10:57
4591

References
Artifact links
Empty
Referencing story #9411

Artifact Tracker v5

epic #8629 OAuth2 & OpenId Connect
Display settings

Follow-ups