---
title: "exSsoLoginOauth"
canonical: "https://help.agiloft.com/space/HELP/65341036/exSsoLoginOauth"
format: markdown
---
Once the integration is complete, users can access Agiloft CLM with OAuth 2.0 SSO. Follow the steps below to create the OAuth SSO login URL and share it with your users.

1. Create a URL in the following form:
  `https://HOSTNAME/ui/oauth20sso?project=KB+NAME`
2. In the URL, replace HOSTNAME and KB+NAME with the values for your system. Use a plus sign (+) in place of any spaces in the KB name. For example:
  `https://example.agiloft.com/ui/oauth20sso?project=Example+KB+Name`

> 📝 To customize where users are directed after signing in, you can include additional keywords in the SSO login URL. For information, see [Hyperlink Syntax and Examples](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718366).

3. Now, go to the new URL in a browser. If you are already authenticated with the IdP, you're forwarded directly to the Agiloft CLM user interface. If you're not logged in to the IdP, you're forwarded to the IdP login page.
4. Depending on how you want users to access Agiloft CLM, you can choose one or more of the following options:
  - Send the URL to all users who should log in via SP-initiated OAuth SSO and ask them to bookmark it or add it to their favorites.
  - Add the URL to an existing webpage if you use a [custom login method](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/925466673). Then direct users to that page.
  - Set up IdP-initiated SSO and send users to the IdP to access Agiloft CLM. Refer to the documentation for your IdP to set up IdP-initiated SSO.
5. For logins from Agiloft Contract Assistant applications, tell users to click Login via OAuth.
6. If you manually created other hyperlinks for use in the system, you need to update those links to accommodate both SSO logins and standard login users. This step is only necessary for links you manually created. See [Hyperlink Syntax and Examples](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718366).

> ℹ️ For system-generated email hotlinks, you don't have to make any changes to accommodate SSO and non-SSO users. Based on a user's login method, Agiloft CLM manages which hotlink URL they receive in email. Each time a user logs in, the system sets a hidden SSO Authentication Method field in the user's record. If a user logs in with a standard username and password, the value is `STANDARD`. If a user logs in with OAuth 2.0 SSO, the value is `OAUTH20`. This value determines whether email hotlinks go to `login.jsp` or `oauth20sso`. Don't edit a user's SSO Authentication Method because you might prevent them from accessing the system.

7. Finally, to make sure users can't circumvent SSO and log in to Agiloft directly, follow the instructions in [Force SSO Login](#force_sso) below.