Configure Secret Server (on-premises) for Single sign-on with Microsoft Entra ID

In this article, you learn how to integrate Secret Server (on-premises) with Microsoft Entra ID. When you integrate Secret Server (on-premises) with Microsoft Entra ID, you can:

• Control in Microsoft Entra ID who has access to Secret Server (on-premises).
• Enable your users to be automatically signed-in to Secret Server (on-premises) with their Microsoft Entra accounts.
• Manage your accounts in one central location.

Prerequisites

The scenario outlined in this article assumes that you already have the following prerequisites:

• A Microsoft Entra user account with an active subscription. If you don't already have one, you can Create an account for free.
• One of the following roles:
  • Application Administrator
  • Cloud Application Administrator
  • Application Owner.

• Secret Server (on-premises) single sign-on (SSO) enabled subscription.

Scenario description

In this article, you configure and test Microsoft Entra SSO in a test environment.

• Secret Server (on-premises) supports SP and IDP initiated SSO.

Add Secret Server (on-premises) from the gallery

To configure the integration of Secret Server (on-premises) into Microsoft Entra ID, you need to add Secret Server (on-premises) from the gallery to your list of managed SaaS apps.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Browse to Entra ID > Enterprise apps > New application.
3. In the Add from the gallery section, type Secret Server (On-Premises) in the search box.
4. Select Secret Server (On-Premises) from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, and walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.

Configure and test Microsoft Entra SSO for Secret Server (on-premises)

Configure and test Microsoft Entra SSO with Secret Server (on-premises) using a test user called B.Simon. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Secret Server (on-premises).

To configure and test Microsoft Entra SSO with Secret Server (on-premises), perform the following steps:

1. Configure Microsoft Entra SSO - to enable your users to use this feature.
   1. Create a Microsoft Entra test user - to test Microsoft Entra single sign-on with B.Simon.
   2. Assign the Microsoft Entra test user - to enable B.Simon to use Microsoft Entra single sign-on.
2. Configure Secret Server (On-Premises) SSO - to configure the single sign-on settings on application side.
   1. Create Secret Server (On-Premises) test user - to have a counterpart of B.Simon in Secret Server (on-premises) that's linked to the Microsoft Entra representation of user.
3. Test SSO - to verify whether the configuration works.

Configure Microsoft Entra SSO

Follow these steps to enable Microsoft Entra SSO.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

2. Browse to Entra ID > Enterprise apps > Secret Server (On-Premises) application integration page, find the Manage section and select Single sign-on.

3. On the Select a Single sign-on method page, select SAML.

4. On the Set up Single Sign-On with SAML page, select the pencil icon for Basic SAML Configuration to edit the settings.

   

5. On the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:

   a. In the Identifier text box, type the URL: https://secretserveronpremises.azure

   b. In the Reply URL text box, type a URL using the following pattern: https://<SecretServerURL>/SAML/AssertionConsumerService.aspx

   Note

   The Entity ID shown above is an example only and you're free to choose any unique value that identifies your Secret Server instance in Microsoft Entra ID. You need to send this Entity ID to Secret Server (On-Premises) Client support team and they configure it on their side. For more details, please read this article.

6. Select Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:

   In the Sign-on URL text box, type a URL using the following pattern: https://<SecretServerURL>/login.aspx

   Note

   These values aren't real. Update these values with the actual Reply URL and Sign-On URL. Contact Secret Server (On-Premises) Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section.

7. On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate and save it on your computer.

   

8. On the Set up Single Sign-On with SAML page, select the Edit icon to open SAML Signing Certificate dialog.

   

9. Select Signing Option as Sign SAML response and assertion.

   

10. On the Set up Secret Server (On-Premises) section, copy one or more appropriate URLs based on your requirement.

    

Create and assign Microsoft Entra test user

Follow the guidelines in the create and assign a user account quickstart to create a test user account called B.Simon.

Configure Secret Server (on-premises) SSO

To configure single sign-on on the Secret Server (On-Premises) side, you need to send the downloaded Certificate (Base64) and appropriate copied URLs to the Secret Server (on-premises) support team. They set this setting to have the SAML SSO connection set properly on both sides.

Create Secret Server (on-premises) test user

In this section, you create a user called Britta Simon in Secret Server (on-premises). Work with Secret Server (on-premises) support team to add the users in the Secret Server (on-premises) platform. Users must be created and activated before you use single sign-on.

Test SSO

In this section, you test your Microsoft Entra single sign-on configuration with following options.

SP initiated:

• Select Test this application, this option redirects to Secret Server (on-premises) Sign-on URL where you can initiate the sign-in flow.

• Go to Secret Server (on-premises) Sign on URL directly and initiate the sign-in flow from there.

IDP initiated:

• Select Test this application, and you should be automatically signed in to the Secret Server (on-premises) for which you set up the SSO.

You can also use Microsoft My Apps to test the application in any mode. When you select the Secret Server (on-premises) tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the sign-in flow and if configured in IDP mode, you should be automatically signed in to the Secret Server (on-premises) for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.

Related content

Once you configure Secret Server (on-premises) you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Defender for Cloud Apps.