Before you start, make sure you have a GitHub developer account (opens new window).
To connect to GitHub social login, you need:
- Create a GitHub OAuth application
- Configure the GitHub social login application in the Authing console
# Create a GitHub OAuth application
Please follow the GitHub 文档 (opens new window)Guide to create a GitHub OAuth application, you need to record the Client ID and Client Secret，of the application , which will be used later.。
When creating an application, please use the following settings:
|Authorization callback URL|
Replace <YOUR_USERPOOL_ID> with your user pool ID.
# Configure the GitHub social login application in the Authing console
Find the GitHub application in the Authing console（connect identity source - social login）and fill in the configuration of the GitHub OAuth application:
Callback URL：This is your business callback domain name, which is different from the callback link configured in the social login application.For example, your website domain name is https://example.com, and the url for processing Authing callback requests is /auth/callback, then you should fill in as
https://example.com/auth/callback. If you need to configure the callback link separately in the application, the address here can be filled in: #.
Scopes(Optional): By default, Authing will only request authorization from users for basic user information (such as avatar, nickname, email, etc.). If you need more advanced permissions, you can check the corresponding options. For details, please refer to Configure Login Authorization Scopes.
After configuration, please click "OK" to save the information.
After the configuration is complete, you can start to formally integrate social login into your system. Authing social login supports four access methods: using JavaScrit SDK, using Guard for Web login form component, using Authing online login page As with manually calling the social login interface, for the applicable scenarios and advantages and disadvantages of each method, please refer to: Social Login Access Guide.