If your organization uses an Identity Provider (IdP) not listed among our pre-configured integrations (such as PingFederate, CyberArk, ForgeRock, Shibboleth, or an internal identity system), you can integrate it with Atatus using standard SAML 2.0.

What You Will Need

Before you begin, verify that you have:
  • An Atatus account with the Owner or Admin role (account.sso.manage permission).
  • Administrative access to create and manage applications in your Identity Provider.

Step 1: Get Service Provider Values from Atatus

  1. Log in to your Atatus dashboard.
  2. Navigate to Settings » Account Settings » Single Sign-on.
  3. Keep this tab open. Copy and record the following parameters:

Step 2: Configure Your Identity Provider

In your IdP management console, create a new SAML 2.0 connector and enter the following settings:

General & Connection Settings

  • SAML Version: 2.0
  • Assertion Consumer Service (ACS) URL: Paste the Atatus SAML ACS URL.
  • Entity ID / Audience Restriction: Paste the Atatus Account Id.
  • Recipient URL / Destination URL: Paste the Atatus SAML ACS URL.
  • NameID Format: Select EmailAddress (urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress) or Unspecified.
  • NameID Value: Map to the user’s primary corporate email address.
  • SAML Binding: HTTP-POST for assertions; HTTP-Redirect for AuthnRequests.
  • Signature Algorithm: RSA-SHA256. Atatus requires signed SAML responses or signed assertions.

Step 3: Configure SAML Attribute Mapping

Atatus reads user profile information from the SAML assertion. Configure your IdP to release the following attributes:
Important Attribute Notes:
  • Atatus matches attributes strictly by exact Name. FriendlyName values are ignored.
  • WS-Federation claims (such as http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress or givenName/surname) are not accepted by Atatus. Configure plain attribute names as shown above.
  • Role or group claims are not evaluated. All new users provisioned via SSO start with the User role.

Step 4: Assign Users in Your IdP

Ensure users and groups who require access to Atatus are granted access in your IdP application assignment settings.

Step 5: Export IdP Metadata

Obtain your IdP SAML metadata using one of the following methods:
  • SAML Metadata URL: A publicly accessible HTTPS URL hosting the IdP’s XML federation descriptor.
  • SAML Metadata XML File: A downloaded XML document containing the IdP’s Entity ID, HTTP-POST SingleSignOnService endpoints, and public X.509 signing certificate.
Single Signing Certificate Requirement: Ensure your IdP metadata contains only one active signing certificate. Descriptors containing multiple active signing certificates will cause signature validation failure in Atatus.

Step 6: Add Metadata in Atatus

  1. In the Atatus dashboard, return to Settings » Account Settings » Single Sign-on.
  2. Under SAML Metadata from your SSO provider:
    • Select SAML Metadata URL and enter your public metadata endpoint, or
    • Select SAML Metadata XML, click Choose File, and upload your downloaded metadata XML file.
  3. Click Save SSO.
  4. Verify that the Enabled toggle switch displays active.
Set an Account Alias: Enter a memorable identifier (minimum 4 characters, for example: my-org) in the SSO Account ID Alias field and click Save Alias. This generates a simplified login URL: https://app.atatus.com/login/saml/my-org.

Step 7: Test the SSO Configuration

Always verify your configuration in an incognito or private browsing window:

Test SP-Initiated Login

  1. Open an incognito browser window.
  2. Navigate to your Atatus custom sign-in URL: https://app.atatus.com/login/saml/<ACCOUNT_ID_OR_ALIAS>.
  3. Confirm that you are redirected to your IdP sign-in screen.
  4. Authenticate with an assigned user account.
  5. Verify that authentication succeeds and opens the Atatus dashboard.

Test IdP-Initiated Login

  1. Sign in to your corporate identity dashboard.
  2. Click the Atatus application connector.
  3. Confirm that a new browser tab opens and logs you into Atatus.