![]() Instead, this step of the flow will automatically complete with the set of scopes the user has authorized for the application. For users who have authorized scopes for the application, the user won't be shown the OAuth authorization page with the list of scopes. If not provided, scope defaults to an empty list for users that have not authorized any scopes for the application. Suggests a specific account to use for signing in and authorizing the app.Ī space-delimited list of scopes. The URL in your application where users will be sent after authorization. The client ID you received from GitHub when you registered. When your GitHub App specifies a login parameter, it prompts users with a specific account they can use for signing in and authorizing your app. Your app accesses the API with the user's access token.Users are redirected back to your site by GitHub.Users are redirected to request their GitHub identity.The web application flow to authorize users for your app is: See " Identifying and authorizing users for GitHub Apps" for more information. Note: If you are building a GitHub App, you can still use the OAuth web application flow, but the setup has some important differences.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |