SSO Configuration

SSO(Single Sign-On) Authentication

Supported Providers

• Google
• GitHub

Google Console Configuration

1. Navigate to the Google Cloud Console.
2. Go to APIs & Services > Credentials > Create Credentials.
3. Create a new OAuth Client ID.
4. Configure the allowed domains:
   • Authorized JavaScript origins: https://<your-domain>
   • Authorized redirect URIs: https://<your-domain>/auth/google/callback

GitHub Console Configuration

1. Navigate to the GitHub Developer Settings.
2. Go to OAuth Apps > New OAuth App.
3. Fill in the required fields:
   • Application name: Your application name
   • Homepage URL: https://<your-domain>
   • Application description: Your application description
   • Authorization callback URL: https://<your-domain>/auth/github/callback

Detailed Guides

• Google SSO Setup
• GitHub SSO Setup

How to Get Google Client ID and Client Secret

Adding Google sign-in to your site simplifies the login process for your users, allowing them to sign in with a single click. To integrate Google OAuth, you'll need a Client ID and a Client Secret.

Note: You must be signed in to your Google account to generate these credentials.

Step 1: Open Developer Console

Go to the Google Developers Console page.

Step 2: Create a New Project

Click on the Select a project dropdown at the top, select New Project, and click Create.

Step 3: Name Your Project

Enter your Project name and click Create.

Step 4: Configure OAuth Consent Screen

Click OAuth consent screen in the left sidebar. Choose the User Type (usually "External") and click Create.

Step 5: Fill in App Information

Provide the following details:

• Application name: The name of your website or app.
• Support email: Your contact email.
• Authorized domain: Your website's domain.
• Developer contact information: Your email address.

Click Save and Continue.

Step 6: Complete Registration

Complete all four steps in the OAuth consent screen wizard and then click Back to Dashboard.

Step 7: Create Credentials

Go to the Credentials tab, click Create Credentials, and select OAuth client ID from the dropdown menu.

Step 8: Select Application Type

Under Application type, select Web application and enter a name for your OAuth 2.0 client.

Step 9: Configure Origins and Redirects

• Authorized JavaScript origins: Enter your site's URL.
• Authorized redirect URIs: Enter the URL where users should be redirected after authenticating with Google.

Click Create to proceed.

Step 10: Secure Your Credentials

Your Client ID and Client Secret will be generated. Copy and save them immediately, as the secret will not be shown again once you leave the page.

How to Get GitHub Client ID and Client Secret

Adding GitHub sign-in to your site simplifies the login process for your users, allowing them to sign in with a single click. To integrate GitHub OAuth, you'll need a Client ID and a Client Secret.

Note: You must be signed in to your GitHub account to generate these credentials.

Step 1: Open Developer Settings

Go to the GitHub Developer Settings page.

Step 2: Create a New OAuth App

Click on OAuth Apps in the left sidebar, then click the New OAuth App button.

Step 3: Register Your Application

Fill in the following details:

• Application name: The name of your website or app.
• Homepage URL: The full URL to your site's homepage (e.g., https://example.com).
• Application description: (Optional) A brief description of your app.
• Authorization callback URL: The URL where GitHub should redirect users after authentication (e.g., https://example.com/login/github/callback).
• Enable Device Flow: (Optional) Enable this if your app needs to support device authentication.

Click Register application to proceed.

Step 4: Retrieve Your Client ID

Once the application is created, your Client ID will be displayed automatically on the application settings page.

Step 5: Generate a Client Secret

The Client Secret is not created by default. To generate one, click the Generate a new client secret button.

Step 6: Secure Your Client Secret

Your new client secret will be displayed. Copy and save it immediately, as it will not be shown again once you leave the page.