Close
logodocs

SSO With SAML

Overview

This guide provides instructions to set up single sign-on (SSO) using the SAML 2.0 (Security Assertion Markup Language) login standard. A successful configuration allows authentications between strongDM as the service provider (SP) and the identity provider (IdP) of your choice.

Features

Basic features

  • Users must authenticate with SSO every time they log in to strongDM. Authentications from previous sessions cannot be reused.

Advanced features

  • The current SAML integration uses SHA-256 with RSA signature encryption.
  • Email address serves as the default user ID in the SAML assertion.
  • A RelayState HTTP parameter cannot be included as part of the SAML request and response.

Unsupported features

  • IdP-initiated authentication is currently not supported. The user must initiate the login from strongDM.
  • The direct upload of an SSO provider's metadata file is not available.

Prerequisites

To get started, make sure the following conditions are met:

  • In your identity provider, you must have elevated privileges or be an administrator with the ability to manage application settings.
  • In strongDM, your permission level must be set to Administrator.
  • Ensure you have a unique identifier for users. Only email address is currently supported.

Configure strongDM

Use the following steps to configure strongDM to work with your IdP. Once the SAML feature is enabled in strongDM, these values can be copied to the configuration settings used for your IdP.

  1. In the strongDM Admin UI, go to Settings > User Management.
  2. Click the Lock icon to make changes.
  3. Click Yes to enable single sign-on.
  4. Select SAML from the Provider dropdown. With this setting, users log in to strongDM using your IdP and the SAML protocol.
User Management Configure SAML
User Management Configure SAML
  1. Verify the settings listed in the Single Sign-on section. Read-only fields are automatically generated based on your organization. You can copy these pre-populated values and paste them into the matching configuration settings found in your IdP interface.

    The Metadata URL field typically comes from your IdP configuration and is required for strongDM and the IdP to communicate. Follow the steps in the Add SAML Metadata section to add this URL value in strongDM.

    FieldExample ValueDescription
    Metadata URLhttps://app.onelogin.com/saml/metadata/<RANDOM_STRING>Public URL where strongDM can request metadata for an IdP's SAML configuration in order to communicate with the IdP; establishes trust by allowing strongDM to correctly sign and validate signatures from the IdP
    strongDM Metadata URLhttps://app.strongdm.com/saml/<ORG_NAME>/metadataPublic URL where the IdP can request metadata for strongDM's SAML configuration in order to communicate with strongDM; establishes trust by allowing the IdP to correctly sign and validate signatures from strongDM
    Entity IDhttps://app.strongdm.com/spString that uniquely identifies strongDM as the SP entity to receive the SAML authentication message from the IdP
    ACS (Consumer) URLhttps://app.strongdm.com/saml/<ORG_NAME>/acsThe strongDM Assertion Consumer Service (ACS) endpoint where the IdP sends its authentication response; responsible for receiving and parsing the SAML assertion
  2. Select the desired general SSO settings.

  3. Leave the strongDM browser window open until you can obtain the Metadata URL from your identity provider.

Configure the Identity Provider

In general, you must consider the following items to configure SAML in your IdP dashboard and to create a successful SAML integration. These steps may differ from identity provider to identity provider.

  1. On the IdP side, add strongDM as an application that leverages SAML SSO.

  2. Once the strongDM application is created in your IdP admin dashboard, configure the SAML settings in your identity provider. There may be additional settings to consider, but you can start by copying and pasting the values generated in step 4 of the Configure strongDM section:

    • strongDM Metadata URL
    • Entity ID
    • ACS (Consumer) URL
  3. Confirm that the email addresses for all users are identical in both strongDM and your identity provider.

  4. To ensure users can access all intended resources, you may have to add each user to the strongDM application created in your identity provider.

  5. Once you have configured settings in your IdP, continue with the next section to add your SAML metadata to strongDM.

Add SAML Metadata

SPs and IdPs swap XML metadata to share configurations, establish trust, and communicate with each other. For this purpose, you can copy the SAML metadata from your identity provider to the SSO section in the strongDM Admin UI. After configuring the application settings in your identity provider, use these steps to add the IdP metadata URL to strongDM. This value is required for your SSO configuration to work correctly.

  1. Find the IdP metadata URL in your identity provider.
  2. Go to the strongDM browser window you left open while configuring the SAML settings in the Admin UI.
  3. In the Single Sign-on section, paste the copied IdP metadata URL from your identity provider into the Metadata URL field in strongDM.
  4. Click Save to complete the setup.

The SAML metadata is currently cached for three hours. If any configuration changes are made, they may not appear immediately.

Troubleshooting

When troubleshooting your SAML integration, note that the following can prevent successful user logins:

  • The correct SAML metadata URL must be added in strongDM. If this URL is incorrect, you may get errors that the XML is invalid during login attempts.
  • If the application is misconfigured or the field values are wrong in your IdP, you can get a permission denied error in strongDM. This error may also display if the user is not added to the app in your IdP.

If any errors occur or if the integration fails in any way, please contact support@strongdm.com for assistance.

Installation — Previous
SSO With OneLogin (SAML)
Next — Installation
SSO With VMware Workspace ONE