--- title: "SAML" slug: "saml" updated: 2025-02-06T19:50:55Z published: 2025-02-06T19:50:55Z canonical: "skthelp.syniti.com/saml" --- > ## 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. # SAML ## Overview Security Assertion Markup Language (SAML) 2.0 is an open standard that facilitates single sign-on (SSO) to provide authentication and authorization to any resources in the Syniti Knowledge Platform (SKP) using your organization’s identity provider (IdP). SAML 2.0 uses eXtensible Markup Language (XML) to encode the assertions, user information, and messages. With SAML 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 SAML SSO, but are not limited to: - Microsoft Entra ID (formerly Azure Active Directory). Refer to [Configuring SAML SSO with Microsoft Entra ID](/v1/docs/saml-sso-with-microsoft-entra-id-for-the-skp) for information on SSO integration with the SKP. - Okta - PingFederate - SiteMinder > [!NOTE] > Note > > Any identity provider using the SAML 2.0 protocol is also supported. ## Configure SAML SSO using an IdP You can use your organization’s IdP to configure SAML SSO with the SKP. This section describes the data required from your organization’s IdP and the SKP to set up the SAML 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 the SKP-initiated sign-on page to configure the SAML settings in the SKP. > [!NOTE] > Note > > - This SKP Administrator account must be the initial administrator account that uses a trusted domain sent to you during the provisioning process by 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 must [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 SAML authentication request is valid for a limited time. Therefore, ensure that your IdP server’s time is synchronized with Network Time Protocol (NTP). > [!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 SAML Metadata URLs that match your SKP tenant region: | SKP Tenant Region | Entity ID | Assertion Consumer Service URL | Single Logout Service URL | Syniti’s SAML Certificate | | --- | --- | --- | --- | --- | | Americas | `syniti.com` | `https://api.syniti.com/oauth/signin/callback` | `https://api.syniti.com/oauth/signout/callback` | Use the certificate information from the following Syniti’s SAML metadata URL: [**https://api.syniti.com/saml/metadata.xml**](https://api.syniti.com/saml/metadata.xml) | | Australia | `syniti.au` | `https://api.syniti.au/oauth/signin/callback` | `https://api.syniti.au/oauth/signout/callback` | Use the certificate information from the following Syniti’s SAML metadata URL: [**https://api.syniti.au/saml/metadata.xml**](https://api.syniti.au/saml/metadata.xml) | | EMEA | `syniti.eu` | `https://api.syniti.eu/oauth/signin/callback` | `https://api.syniti.eu/oauth/signout/callback` | Use the certificate information from the following Syniti’s SAML metadata URL: [**https://api.syniti.eu/saml/metadata.xml**](https://api.syniti.eu/saml/metadata.xml) | | Canada | `syniti.ca` | `https://api.syniti.ca/oauth/signin/callback` | `https://api.syniti.ca/oauth/signout/callback` | Use the certificate information from the following Syniti’s SAML metadata URL: [**https://api.syniti.ca/saml/metadata.xml**](https://api.syniti.ca/saml/metadata.xml) | - Entity ID - Assertion Consumer Service URL - Single Logout Service URL - SAML Certificate 3. Add 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 your organization’s IdP Metadata URL or .xml file. The Metadata URL or .xml file must contain the following details of your organization’s IdP: - Entity ID - Assertion Consumer Service or SSO URL - Single Logout Service URL - SAML Certificate - User Metadata Attributes ### Set Up SAML 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%3A37%3A44Z&se=2026-11-17T20%3A37%3A44Z&sr=b&sp=r&sig=VuYnqe8r6SRsBH%2F02aOQWE0syG84VRbMbFIQd3J%2FMKY%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%3A37%3A44Z&se=2026-11-17T20%3A37%3A44Z&sr=b&sp=r&sig=kb55qeLwFVMCdUs5QefTdqnQdqwDGGrurz0LsQHYEOU%3D) 4. Click **Configure SSO**. The Edit Single Sign On dialog box is displayed. 5. Select the **SAML 2.0** option to enable the fields related to SAML SSO configuration. > [!WARNING] > Important! > > Once you save your SAML SSO configuration, you cannot switch to the OpenID Connect (OIDC) protocol. Ensure that you select the SSO protocol correctly. > > To switch to the OIDC protocol, you must contact [Syniti Support](/v1/docs/contact-support). ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image(591).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A44Z&se=2026-11-17T20%3A37%3A44Z&sr=b&sp=r&sig=KuTnGarfSvDHdeJaVsDG6op42wvVbzEcKl9DRERE%2B1E%3D) 6. In the *SSO Configuration Name* field, enter a unique name for your organization. 7. In the *Metadata URL* field, enter the Metadata URL that you’ve obtained from your organization’s IdP. 8. If you prefer to use the metadata .xml file, click the **Switch to Metadata XML File** button and enter the Metadata’s XML code that you’ve obtained from your organization’s metadata .xml file. > [!NOTE] > Note > > Syniti recommends using a URL link for the Metadata so that the metadata be can automatically monitored for updates. 9. In the *User Metadata Attributes* section, enter the below URLs to the corresponding fields on the page: | Field Name in the SKP | Description | Example SAML Attribute URL in the Metadata | | --- | --- | --- | | Name | The Display Name endpoint of the user. | `http://schemas.microsoft.com/identity/claims/displayname` | | Email Address | The Email Address endpoint of the user. | `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` | | Identifier | The Primary Identifier endpoint for the user in the directory. It must be immutable and globally unique. | `http://schemas.microsoft.com/identity/claims/objectidentifier` | > [!NOTE] > Note > > You can obtain the above attributes from your organization’s Metadata URL or .xml file. 10. Select **Save** to complete your SSO configuration in the SKP. 11. 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(598).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A37%3A44Z&se=2026-11-17T20%3A37%3A44Z&sr=b&sp=r&sig=UwIX9WdFjAccqjP6LqG%2FhfMBLOWdGkHTCEjumUHX3gs%3D) ## Verify Your SAML SSO Configuration When you turn on the **Active** toggle button on the *Single Sign-On* page, Syniti enables the SSO feature for the 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 to its database and lets you sign in to the SKP. If the entered email address is new, 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 SAML 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 SAML SSO Configuration](/v1/docs/troubleshoot-your-saml-sso-configuration) to troubleshoot your SSO configuration and test again in an incognito window. ## Next Steps Now that you have configured and verified your SAML 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.