About 63 results: "gitlab oauth2"
Page 1 of 4
Filter Results
Sources
Languages
Lines
Any number of lines
Try Search On








  1. ## GitLab as OAuth2 authentication service provider
  2. 
                        
  3. This document is about using GitLab as an OAuth authentication service provider to sign into other services.
  4. If you want to use other OAuth authentication service providers to sign into GitLab please see the [OAuth2 client documentation](../api/oauth2.md)
  5. 
                        
  6. OAuth2 provides client applications a 'secure delegated access' to server resources on behalf of a resource owner. Or you can allow users to sign in to your application with their GitLab.com account.
  7. with the approval of the resource owner, or end-user. 
  8. Mostly, OAuth2 is using for SSO (Single sign-on). But you can find a lot of different usages for this functionality. 
  9. For example, our feature 'GitLab Importer' is using OAuth protocol to give an access to repositories without sharing user credentials to GitLab.com account. 
  10. Also GitLab.com application can be used for authentication to your GitLab instance if needed [GitLab OmniAuth](gitlab.md).
  11. 
                        
  12. GitLab has two ways to add new OAuth2 application to an instance, you can add application as regular user and through admin area. So GitLab actually can have an instance-wide and a user-wide applications. There is no defferences between them except the different permission levels.
  13. 
                        
  14. After this you will see application form, where "Name" is arbitrary name, "Redirect URI" is URL in your app where users will be sent after authorization on GitLab.com.












Back to Top