---
title: "Google OAuth 2.0 and OIDC SSO Setup"
canonical: "https://help.agiloft.com/space/HELP/43716014/Google+OAuth+2.0+and+OIDC+SSO+Setup"
format: markdown
---
Agiloft CLM supports single sign-on (SSO) with Google OAuth 2.0 and OpenID Connect (OIDC) for authentication and identification. This article guides you through the steps to create a Google OAuth client for Agiloft CLM and then configure your KB to route SSO logins to Google as the identity provider (IdP). It also includes instructions on how to log in with SSO after the integration and make sure other users log in with SSO as well.

> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - To complete the setup, you need admin access to the Google Cloud Console with permission to configure new applications.
> ℹ️ - Users can't log in with OAuth 2.0 SSO unless they already have a user record in Agiloft CLM. Before setting up SSO, make sure each user who will use SSO has a user record in your KB. You can set up SCIM provisioning to create and update user records automatically. See [Provision Users with SCIM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779649034) for details.
> ℹ️ - Also make sure the data in user records meet at least one of the following conditions. These conditions are used to match users for identification in Google:
> ℹ️   - The user's Email address in Agiloft matches their Gmail address.
> ℹ️   - The user's Login in Agiloft matches their Google login.

# Set Up SSO in Google

Follow the steps below to create a project in Google and add Agiloft as an OAuth web client.

> ℹ️ If the options you see in the console or your practices for adding OAuth 2.0 clients differ from those described here, refer to Google's [documentation](https://developers.google.com/identity/openid-connect/openid-connect) on OpenID Connect to complete the task.

1. Log into the [Google Cloud Platform Console](https://console.cloud.google.com/) as an administrator and go to APIs & Services.
2. Create a new project:
  1. At the top of the screen, click the current project name to open the Select a resource dialog box.
  2. In the dialog box, click New project.
  3. Enter a project name, such as Agiloft SSO, and change the Organization and Location if needed.
  4. Click Create. After the project is created, make sure it's selected at the top of the screen.
3. Next, create the consent screen for the new project. For information on consent screens, refer to Google's [documentation](https://developers.google.com/workspace/guides/configure-oauth-consent) on setting up consent screens.
  1. In the left sidebar, click OAuth consent screen, then click Get Started to configure the project.
  2. Under App information, enter the name of the application, such as Agiloft.
  3. In User support email, select the email address where users can get support, then click Next.
  4. Under Audience, select Internal to limit access to the app to users within your organization, then click Next.
  5. Under Contact information, enter the email address where Google should send project notifications, then click Next.
  6. Agree to the Google API Services User Data policy and click Continue.
  7. Click Create. The OAuth Overview is displayed.
4. Next, click Branding in the sidebar. For information on branding, refer to Google's [documentation](https://support.google.com/cloud/answer/15549049?hl=en) on managing OAuth app branding.
  1. For the App domain settings, you can enter the following URLs for Agiloft's home page, privacy policy, and terms of service:
    - [https://www.agiloft.com/](https://www.agiloft.com/)
    - [https://www.agiloft.com/privacy-policy/](https://www.agiloft.com/privacy-policy/)
    - [https://www.agiloft.com/terms-of-service/](https://www.agiloft.com/terms-of-service/)
  2. For Authorized Domains, add each applicable domain:
    - Add your company domain.
    - If your KB is in the Agiloft domain or you included Agiloft URLs in App domains, add `agiloft.com`.
    - If the domain for your KB is not `agiloft.com` or your company's domain, also add the KB domain.
  3. Click Save to save the changes.
5. Next, create the Agiloft web client:
  1. Click Clients in the sidebar, then click Create Client at the top of the screen.
  2. For Application type, select Web application.
  3. Enter a Name for the client, such as Agiloft SSO Client.
  4. Leave Authorized JavaScript origins blank.
  5. Under Authorized redirect URIs, click Add URI and enter the following URI: `https://HOSTNAME/ui/oauth20sso`. Replace HOSTNAME with the hostname for your Agiloft CLM instance. For example: `https://example.agiloft.com/ui/oauth20sso`. Copy this URI to a note to use later in the setup.
  6. Click Create.
  7. Once the client is created, copy the Client ID to your note. In addition, view the client details and copy the Client secret value to the note.
6. Complete any other optional client configuration as needed. Agiloft client does not require specific Data Access scopes.

Now that the application is configured in Google, you can set up SSO in Agiloft.

# > Macro (anchor)

Set Up SSO in Agiloft CLM

Follow the steps below to set up SSO in Agiloft CLM.

1. Go to **Setup > Access > Configure OAuth 2.0 Profiles** and click New to add a profile.
2. Leave the "Use full OAuth account name as a KB login name / email" checkbox selected.
3. Enter a name for the OAuth 2.0 provider, such as Google.
4. For the role of this OAuth 2.0 Provider, select OAuth20_SSO.
5. Complete the remaining fields:
  1. **Redirect URI**: Overwrite the default value with the Authorized redirect URI you noted when you set up Google.
  2. **Client ID / Application ID / Consumer Key**: The Client ID from your note.
  3. **Client / Consumer Secret**: The Client secret from your note.
  4. **Authentication URI**: Enter Google's authentication endpoint: `https://accounts.google.com/o/oauth2/auth`
  5. **Token URI**: Enter Google's token endpoint: `https://accounts.google.com/o/oauth2/token`
6. Click Finish to save the profile.
7. Finally, make sure each user who will log in with SSO has a user record in Agiloft CLM. Make sure the Email address in the record matches the user's Gmail address or the Agiloft Login matches their Google login. One of the two values must match for identification. For information about creating user records, see [User Management](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/926744591).

Agiloft is now configured to allow SSO with Google OAuth 2.0 and OIDC. Proceed to [Log in with SSO](#sso_login) for details on how to log in.

# > Macro (anchor)

Log in with SSO

> Macro (include)

# > Macro (anchor)

Force SSO Login

> Macro (include)

#### Related articles

> Macro (contentbylabel)