Tutorial: Microsoft Entra SSO integration with Keeper Password Manager

In this tutorial, you'll learn how to integrate Keeper Password Manager with Microsoft Entra ID. When you integrate Keeper Password Manager with Microsoft Entra ID, you can:

• Control in Microsoft Entra ID who has access to Keeper Password Manager.
• Enable your users to be automatically signed-in to Keeper Password Manager with their Microsoft Entra accounts.
• Manage your accounts in one central location.

Prerequisites

To get started, you need the following items:

• A Microsoft Entra subscription. If you don't have a subscription, you can get a free account.
• Keeper Password Manager single sign-on (SSO) enabled subscription.

Scenario description

In this tutorial, you configure and test Microsoft Entra single sign-on in a test environment.

• Keeper Password Manager supports SP-initiated SSO.
• Keeper Password Manager supports Automated user provisioning and deprovisioning (recommended).
• Keeper Password Manager supports just-in-time user provisioning.

Add Keeper Password Manager from the gallery

To configure the integration of Keeper Password Manager into Microsoft Entra ID, add the application from the gallery to your list of managed software as a service (SaaS) apps.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Browse to Identity > Applications > Enterprise applications > New application.
3. In Add from the gallery, type Keeper Password Manager in the search box.
4. Select Keeper Password Manager 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, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.

Configure and test Microsoft Entra SSO for Keeper Password Manager

Configure and test Microsoft Entra SSO with Keeper Password Manager by using a test user called B.Simon. For SSO to work, you need to establish a linked relationship between a Microsoft Entra user and the related user in Keeper Password Manager.

To configure and test Microsoft Entra SSO with Keeper Password Manager:

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 Britta Simon.
   2. Assign the Microsoft Entra test user to enable Britta Simon to use Microsoft Entra single sign-on.

2. Configure Keeper Password Manager SSO to configure the SSO settings on the application side.

   1. Create a Keeper Password Manager test user to have a counterpart of Britta Simon in Keeper Password Manager linked to the Microsoft Entra representation of the 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 Identity > Applications > Enterprise applications > Keeper Password Manager application integration page, find the Manage section. 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. In the Basic SAML Configuration section, perform the following steps:

   a. For Identifier (Entity ID), type a URL using one of the following patterns:

   • For cloud SSO: https://keepersecurity.com/api/rest/sso/saml/<CLOUD_INSTANCE_ID>
   • For on-premises SSO: https://<KEEPER_FQDN>/sso-connect

   b. For Reply URL, type a URL using one of the following patterns:

   • For cloud SSO: https://keepersecurity.com/api/rest/sso/saml/sso/<CLOUD_INSTANCE_ID>
   • For on-premises SSO: https://<KEEPER_FQDN>/sso-connect/saml/sso

   c. For Sign on URL, type a URL using one of the following patterns:

   • For cloud SSO: https://keepersecurity.com/api/rest/sso/ext_login/<CLOUD_INSTANCE_ID>
   • For on-premises SSO: https://<KEEPER_FQDN>/sso-connect/saml/login

   d. For Sign out URL, type a URL using one of the following patterns:

   • For cloud SSO: https://keepersecurity.com/api/rest/sso/saml/slo/<CLOUD_INSTANCE_ID>
   • There is no configuration for on-premises SSO.

   Note

   These values aren't real. Update these values with the actual Identifier,Reply URL and Sign on URL. To get these values, contact the Keeper Password Manager Client support team. You can also refer to the patterns shown in the Basic SAML Configuration section.

6. The Keeper Password Manager application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.

   

7. In addition, the Keeper Password Manager application expects a few more attributes to be passed back in SAML response. These are shown in the following table. These attributes are also pre-populated, but you can review them per your requirements.

   Name	Source attribute
   First	user.givenname
   Last	user.surname
   Email	user.mail

8. On Set up Single Sign-On with SAML, in the SAML Signing Certificate section, select Download. This downloads Federation Metadata XML from the options per your requirement, and saves it on your computer.

   

9. On Set up Keeper Password Manager, copy the appropriate URLs, per your requirement.

   

Create a Microsoft Entra test user

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

1. Sign in to the Microsoft Entra admin center as at least a User Administrator.
2. Browse to Identity > Users > All users.
3. Select New user > Create new user, at the top of the screen.
4. In the User properties, follow these steps:
   1. In the Display name field, enter B.Simon.
   2. In the User principal name field, enter the [email protected]. For example, [email protected].
   3. Select the Show password check box, and then write down the value that's displayed in the Password box.
   4. Select Review + create.
5. Select Create.

Assign the Microsoft Entra test user

In this section, you enable B.Simon to use Azure single sign-on by granting access to Keeper Password Manager.

1. Browse to Identity > Applications > Enterprise applications.
2. In the applications list, select Keeper Password Manager.
3. In the app's overview page, find the Manage section and select Users and groups.
4. Select Add user. In Add Assignment, select Users and groups.
5. In Users and groups, select B.Simon from the list of users. Then choose Select at the bottom of the screen.
6. If you're expecting a role to be assigned to the users, you can select it from the Select a role list. If no role has been set up for this app, the Default Access role is selected.
7. In Add Assignment, select Assign.

Configure Keeper Password Manager SSO

To configure SSO for the app, see the guidelines in the Keeper support guide.

Create a Keeper Password Manager test user

To enable Microsoft Entra users to sign in to Keeper Password Manager, you must provision them. The application supports just-in-time user provisioning, and after authentication users are created in the application automatically. If you want to set up users manually, contact Keeper support.

Test SSO

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

• Click on Test this application, this will redirect to Keeper Password Manager Sign-on URL where you can initiate the login flow.

• Go to Keeper Password Manager Sign-on URL directly and initiate the login flow from there.

• You can use Microsoft My Apps. When you click the Keeper Password Manager tile in the My Apps, this will redirect to Keeper Password Manager Sign-on URL. For more information, see Microsoft Entra My Apps.

Next steps

After you configure Keeper Password Manager, you can enforce session control. This protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. For more information, see Learn how to enforce session control with Microsoft Defender for Cloud Apps.