GitHub login setup

Strivacity supports social authentication using external identity providers such as GitHub. This allows customers to log in to your application using their existing GitHub identity.

Step 1: Configuring a GitHub app in the GitHub console

To set up GitHub Sign-in as a social login provider, follow these steps.

1. Begin by logging into your GitHub profile, selecting the Profile icon, then selecting Settings.

Now navigate to Developer settings, as shown in the screenshot below:

2. Next, within Developer Settings, select New GitHub app from the top right-hand corner as shown below:

3. Within the Register new GitHub app screen, complete the following information as shown in the table below:

4. Next, choose Create GitHub app at the bottom of the screen (without changing any other options).

5. Select Generate a new client secret, as shown below.

Step 2: Configuring GitHub sign-in within Strivacity

Following these steps will finalize your setup for using GitHub Sign-in as a social login provider with your application in Strivacity.

1. Start by logging into the Admin Console using an admin account.

2. In the left-hand menu, select Identities, then Social login.

3. Select Create.

4. Select GitHub from the list of available social provider capabilities.

5. Fill in the Configuration for GitHub as a social login provider. Copy the Client ID and Client Secret from the GitHub app configuration, and paste the respective values into the Client ID and Client Secret fields.

6. Select the Scopes to request from GitHub. By default, Strivacity requests access to the GitHub basic profile and can optionally request the customer’s email address.

7. Enable Synchronize and store profile data at each login to ensure customer data is kept up-to-date inside your application. If you choose to synchronize and store this social profile data at each login, Strivacity will retrieve and store this information, which will be visible to the customer on their My Account page and to any Strivacity admins when managing the customer's identity.

8. You can also define Additional parameters that are included in the authorization request sent to GitHub. These parameters allow you to control provider-specific authentication behavior. For example, some providers support parameters such as prompt=login to force re-authentication instead of reusing an existing session.