Tutorial: Integrate Secret Server (On-Premises) with Azure Active Directory

In this tutorial, you'll learn how to integrate Secret Server (On-Premises) with Azure Active Directory (Azure AD). When you integrate Secret Server (On-Premises) with Azure AD, you can:

• Control in Azure AD who has access to Secret Server (On-Premises).
• Enable your users to be automatically signed-in to Secret Server (On-Premises) with their Azure AD accounts.
• Manage your accounts in one central location - the Azure portal.

Prerequisites

To get started, you need the following items:

• An Azure AD subscription. If you don't have a subscription, you can get a free account.
• Secret Server (On-Premises) single sign-on (SSO) enabled subscription.

Scenario description

In this tutorial, you configure and test Azure AD 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 Azure AD, you need to add Secret Server (On-Premises) from the gallery to your list of managed SaaS apps.

1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
2. On the left navigation pane, select the Azure Active Directory service.
3. Navigate to Enterprise Applications and then select All Applications.
4. To add new application, select New application.
5. In the Add from the gallery section, type Secret Server (On-Premises) in the search box.
6. 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.

Configure and test Azure AD SSO for Secret Server (On-Premises)

Configure and test Azure AD 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 an Azure AD user and the related user in Secret Server (On-Premises).

To configure and test Azure AD SSO with Secret Server (On-Premises), perform the following steps:

1. Configure Azure AD SSO - to enable your users to use this feature.
   1. Create an Azure AD test user - to test Azure AD single sign-on with B.Simon.
   2. Assign the Azure AD test user - to enable B.Simon to use Azure AD 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 is linked to the Azure AD representation of user.
3. Test SSO - to verify whether the configuration works.

Configure Azure AD SSO

Follow these steps to enable Azure AD SSO in the Azure portal.

1. In the Azure portal, on the Secret Server (On-Premises) application integration page, find the Manage section and select Single sign-on.

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

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

   

4. 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 are free to choose any unique value that identifies your Secret Server instance in Azure AD. 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.

5. Click 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 are not 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 in the Azure portal.

6. 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.

   

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

   

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

   

9. On the Set up Secret Server (On-Premises) section, copy the appropriate URL(s) based on your requirement.

   

Create an Azure AD test user

In this section, you'll create a test user in the Azure portal called B.Simon.

1. From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
2. Select New user at the top of the screen.
3. In the User properties, follow these steps:
   1. In the Name field, enter B.Simon.
   2. In the User name field, enter the username@companydomain.extension. For example, B.Simon@contoso.com.
   3. Select the Show password check box, and then write down the value that's displayed in the Password box.
   4. Click Create.

Assign the Azure AD test user

In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Secret Server (On-Premises).

1. In the Azure portal, select Enterprise Applications, and then select All applications.
2. In the applications list, select Secret Server (On-Premises).
3. In the app's overview page, find the Manage section and select Users and groups.
4. Select Add user, then select Users and groups in the Add Assignment dialog.
5. In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
6. If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
7. In the Add Assignment dialog, click the Assign button.

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 from the Azure portal 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 Azure AD single sign-on configuration with following options.

SP initiated:

• Click on Test this application in Azure portal. This will redirect to Secret Server (On-Premises) Sign on URL where you can initiate the login flow.

• Go to Secret Server (On-Premises) Sign-on URL directly and initiate the login flow from there.

IDP initiated:

• Click on Test this application in Azure portal 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 click 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 login 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.

Next steps

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.