--- title: "OpenID Connect" slug: "openid-connect" updated: 2025-02-13T07:32:30Z published: 2025-02-13T07:32:30Z canonical: "skthelp.syniti.com/openid-connect" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # OpenID Connect ## Overview OpenID Connect (OIDC) is an identity layer built based on top of the OAuth 2.0 protocol. OIDC facilitates single sign-on (SSO) to verify the identity of the users based on the authentication performed using your organization’s identity provider (IdP) and authorizes the users to any resources in the Syniti Knowledge Platform (SKP). OIDC uses JavaScript Object Notation (JSON) and JSON Web Token (JWT) to securely transmit information between the SKP and your organization’s IdP. With OIDC SSO, once you log in to the SKP, you are automatically authenticated to different modules and services without needing to log in again. The following IdPs are supported for OIDC SSO, but are not limited to: - Okta. Refer to [Configuring OIDC SSO with Okta](/v1/docs/configuring-oidc-sso-with-okta) for information on SSO integration with the SKP. - Microsoft Entra ID, formerly Azure Active Directory - PingFederate - SiteMinder > [!NOTE] > Note > > Any identity provider using OIDC is also supported. ## Configure OIDC SSO using an IdP You can use your organization’s IdP to configure OIDC SSO with the SKP. This section describes the data required from your organization’s IdP and the SKP to set up the OIDC SSO feature for accessing the SKP. > [!NOTE] > Note > > This article is intended for your organization’s Administrator who also has an Administrator account in the SKP. ### Prerequisites Important! Currently, only the Microsoft Entra ID’s URL (`https://login.microsoftonline.com`) is trusted within Syniti’s network and security policies. To trust your organization’s IdP URL, you have to [submit a request](https://support.syniti.com/hc/en-us/requests/new?ticket_form_id=360000774934&tf_20735434106263=type_request&tf_20735495864983=devops_sso&tf_description=) to Syniti Support. - You must be an SKP Administrator for your tenant that uses SKP-initiated sign-on page to configure the OIDC settings in the SKP. > [!NOTE] > Note > > - This SKP Administrator account must be the initial administrator account (which uses a trusted domain) sent to you during the provisioning process by the Syniti’s Customer Success team. > - If you require additional domains to get added and activated in your tenant for using the SKP-initiated sign-on page, you have to [submit a request](https://support.syniti.com/hc/en-us/requests/new?ticket_form_id=360000774934&tf_20735434106263=type_request&tf_20735495864983=devops_sso&tf_description=) to Syniti Support. - Ensure that you have an Administrator account in your IdP. - Your IdP uses a 2-hour or longer lifespan for session tokens and identity tokens. - For testing purposes, ensure that you create a temporary user account in your organization domain. - Each OIDC authentication request is valid for a limited time. Therefore, ensure that your IdP server’s time is synchronized with Network Time Protocol. - If your organization uses an authenticator tool for multi-factor authentication (MFA) in the IdP, ensure that MFA is active and functioning correctly. > [!NOTE] > Note > > Based on your organization’s IdP, the below SSO configuration may differ. ### Set Up the IdP 1. Create a new application in your organization’s IdP for the SKP. 2. Enter the following data to your IdP using the below Syniti’s Redirect URIs that matches your SKP tenant region: | SKP Tenant Region | Sign-In Redirect URI | Sign-Out Redirect URI | | --- | --- | --- | | Americas | `https://api.syniti.com/oauth/signin/callback` | `https://login.syniti.com/home` | | Australia | `https://api.syniti.au/oauth/signin/callback` | `https://login.syniti.au/home` | | EMEA | `https://api.syniti.eu/oauth/signin/callback` | `https://login.syniti.eu/home` | | Canada | `https://api.syniti.ca/oauth/signin/callback` | `https://login.syniti.ca/home` | - Sign-In Redirect URI - Sign-Out Redirect URI 3. Provision the required users or user groups with the temporary user account to the new application. 4. Save the new application created for the SKP in your organization’s IdP. After saving the IdP configuration, obtain the following details from your organization’s IdP: 1. Client ID 2. Client Secret 3. Issuer URI > [!NOTE] > Note > > Metadata URI can be created using the following format: */.well-known/openid-configuration*. The following data and endpoints can be extracted using the Metadata URI from the registered application in your IdP: > > - Token Scopes > - JWK URL > - Login URL > - Logout URL > - Token URL > - User Metadata Attributes ### Set Up OIDC SSO in the SKP 1. [Log into](https://login.syniti.com/home) the SKP using the Syniti provisioned administrator account to access and log in using the SKP-initiated sign-on page. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(499).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A38%3A02Z&se=2026-11-17T20%3A38%3A02Z&sr=b&sp=r&sig=CXfbo3MOUflC9XkrdXoBiMDdNnd6sO5jDHsOGUyKzHs%3D) SKP-initiated sign-on page 2. Select **Admin** from the *Profile* menu to access the Admin module of the SKP. 3. In the *Admin* menu, click **Single Sign-On**. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(590).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A38%3A02Z&se=2026-11-17T20%3A38%3A02Z&sr=b&sp=r&sig=MaJgS47ZiBSrGqsy16BdAtZBKsxmboKuOXDs3YIba%2Fc%3D) 4. Click **Configure SSO**. The Edit Single Sign On dialog box is displayed. 5. Select the **OIDC** option to enable the fields related to OIDC SSO configuration. > [!WARNING] > Important! > > Once you save your OIDC SSO configuration, you cannot switch to the Security Assertion Markup Language (SAML) 2.0 protocol. Ensure that you select the SSO 2.0 protocol correctly. > > To switch to the SAML 2.0 protocol, you must contact [Syniti Support](/v1/docs/contact-support). ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(592).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A38%3A02Z&se=2026-11-17T20%3A38%3A02Z&sr=b&sp=r&sig=DEUZYgyUUFybdCtBdNzIq%2Bt8qwmIeiollm5qYpto9z8%3D) 6. In the *SSO Configuration Name* field, enter a unique name for your organization. 7. Configure the following OIDC settings: | Field Name | Description | Additional Comments | | --- | --- | --- | | Client ID | Enter the unique identifier issued for the new SKP application by your IdP’s authorization server. | Not applicable | | Client Secret | Client secret used with the Client ID to authenticate the SKP against the IdP’s authorization server. | Copy the Client Secret value from your IdP and paste it into the Client Secret field in the SKP. | | Token Scope | A space-delimited list of scopes to specify the permissions or access rights for the SKP. The following three scope values are *required*: - openid - email - profile | Enter the scope values in the following format: openid email profile | | JWKS URI | The JSON Web Key Set (JWKs) endpoint contains public keys, published by your IdP’s authorization server. The SKP uses these keys to validate the token or key signature against the IdP’s authorization server. | Obtain this endpoint using the *JWKS_URI* attribute from the Metadata URI. This endpoint appears in the following format, but may differ as per your IdP: - "jwks_uri":"https:///keys" - "jwks_uri":"https:///certs" | | Login URL | Login URL required for the users to log into the SKP application configured in your IdP. | Obtain this endpoint using the *authorization_endpoint* attribute from the Metadata URI. This endpoint appears in the following format, but may differ as per your IdP: - "authorization_endpoint":"https:///authorize" - "authorization_endpoint":"https:///auths” | | Logout URL | Logout URL to log out from the SKP configured in your IdP. | Obtain this endpoint using the *end_session_endpoint* attribute from the Metadata URI. This endpoint appears in the following format, but may differ as per your IdP: "end_session_endpoint":"https:///logout" | | Token URL | Token URL for the SKP to exchange an authorization code for an access token on the IdP’s authorization server. | Obtain this endpoint using the *token_endpoint* attribute from the Metadata URI. This endpoint appears in the following format, but may differ as per your IdP: "token_endpoint":"https:///token" | 8. In the *User Metadata Attributes* section, enter the below values to the corresponding fields on the page. The SKP requests these attributes when you include the following scopes in the authorization requests, such as openid, profile, and email. | Field Name | Description | Example Attribute Value in the Metadata | | --- | --- | --- | | Name | Display name of the user. | Enter the claim name as **name**. | | Email Address | Email address of the user. | Enter the claim name as **email**. | | Identifier | Primary identifier for the user in the directory. Immutable and globally unique. | This attribute can vary based on the IdP. Enter the claim name as **sub** or **id**. | 9. Select **Save** to complete your SSO configuration in the SKP. 10. On the *Single Sign-On* page, turn on the **Active** toggle button to activate the SSO configuration for your organization. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(463).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A38%3A02Z&se=2026-11-17T20%3A38%3A02Z&sr=b&sp=r&sig=f%2BYwI5CqAGuKr44ztGf22EpWxqgMvfxyVb7LVvGq4LY%3D) ## Verify Your OIDC SSO Configuration When you turn on the **Active** toggle button on the *Single Sign-On* page, Syniti enables the SSO feature for your users of your organization’s tenant in the SKP. This process does not log out the existing users in the SKP. You don’t need to create a user account for the test user in the SKP, as your organization’s IdP controls and manages the access required for your users in the SKP. The SKP validates the email address used for signing-in in its database and lets you sign in to the SKP. If the entered email address is new, then a new user is assigned to the Default User Group created in the SKP. > [!NOTE] > Note > > By default, only the Viewer user group is assigned to the Default User Group for new tenants. [Edit the user group](https://skthelp.syniti.com/docs/user-groups#edit-a-user-group) to update the Default User Group assignment. If no user groups are set as a Default User Group, users will not be granted access to the SKP. Complete the following steps to verify the OIDC SSO configuration: 1. Open a new incognito or private window in your browser. 2. [Log into](https://login.syniti.com/home) the SKP using the email address of the temporary user account. The IdP-initiated sign-on page is displayed. 3. Complete the login process and confirm you are signed in. If you experience a login error, refer to [Troubleshoot Your OIDC SSO Configuration](/v1/docs/troubleshoot-your-oidc-sso-configuration) to troubleshoot your SSO configuration and test again in an incognito window. ## Next Steps Now that you have configured and verified your OIDC SSO configuration, you can proceed with identifying or adding the required users with appropriate roles in your IdP’s directory. After identifying or adding the required users to your IdP’s directory, you must invite or assign them to the newly created application for the SKP.