Use this guide to connect your IDP to Cognism so your team can sign in to Cognism using single sign-on (SSO).
This guide is intended for Cognism and identity provider (IdP) administrators.
Before you begin
Make sure you have:
- Admin access to Cognism, including the Settings → Authentication page.
- Admin access to your Okta organisation, with permission to create and manage app integrations.
If you use a custom SAML integration
If you previously connected Cognism using a custom SAML integration, your configuration will not carry over to the new sign-in experience. Reconfigure SSO by following this guide.
If you use a different identity provider
This guide uses Okta as an example. Cognism also supports OKTA and ENTRA as IDPs. The configuration process is similar, but the screen names and navigation may differ.
Configure single sign-on
To configure SSO, exchange the Entity ID and Assertion Consumer Service (ACS) URL between Cognism and Okta, then add Okta’s signing certificate to Cognism.
1. Open the SSO settings in Cognism
- In Cognism, go to Settings → Authentication.
- Open the Single Sign-On tab.
- Under Identity provider, find Okta.
- Select Manage or Connect, depending on whether you have already started the setup.
Settings → Authentication → Single Sign-On, with Okta listed as an identity provider.
2. Copy the Entity ID and ACS URL
- In the Okta SSO Configuration dialog, find Step 1.
- Copy the Identifier (Entity ID).
- Copy the ACS URL.
- Leave the dialog open while you configure Okta.
You will add both values to your Okta SAML integration.
The Okta SSO Configuration dialog, showing the Identifier (Entity ID) and ACS URL. Values and certificate are masked.
3. Configure the SAML integration in Okta
- In the Okta Admin Console, go to Applications → Create App Integration.
- Select SAML 2.0 to create a new integration, or open your existing Cognism app.
- Go to the SAML configuration settings.
- Enter the following values:
- Single sign-on URL: Paste the ACS URL from Cognism.
- Recipient URL and Destination URL: Keep Use this for Recipient URL and Destination URL selected.
- Audience URI (SP Entity ID): Paste the Identifier (Entity ID) from Cognism.
- Name ID format: Select EmailAddress.
- Application username: Select Okta username or the appropriate email attribute used by your organisation.
- Complete the remaining required fields and save the configuration.
Okta → Edit SAML Integration → Configure SAML. The ACS URL goes in Single sign-on URL; the Entity ID goes in Audience URI.
4. Download the active Okta signing certificate
- In your Okta app, open the Sign On tab.
- Scroll to SAML Signing Certificates.
- Find the certificate marked Active.
- Open its Actions menu and select Download certificate.
Okta → Sign On → SAML Signing Certificates. Download the certificate marked Active.
5. Add the certificate to Cognism
- Open the downloaded certificate in a plain-text editor.
- Copy the entire certificate contents.
- Return to the Okta SSO Configuration dialog in Cognism.
- Under Step 2, paste the certificate into the X.509 Certificate field.
- Select Configure.
Okta should now appear as Enabled and Connected on the Cognism Authentication page. SSO is configured.
The Cognism Authentication page, showing Okta as Enabled and Connected.
Troubleshooting
Users cannot sign in to Cognism
- Confirm that Okta appears as Enabled and Connected on the Cognism Authentication page.
- Check that the ACS URL and Entity ID in Okta match the values provided by Cognism.
- Confirm that you added the active Okta signing certificate to Cognism.
- Check that the user's Okta account and assigned access are configured correctly.
SSO stopped working after a configuration change
Review the settings in Okta and Cognism. Confirm that the Entity ID, ACS URL and signing certificate are correct and consistent across both systems.
If the issue persists, contact your Cognism administrator or Cognism Support.
Related information
- Configure SSO with Microsoft Entra ID
- Manage Cognism user access and roles