Keeper Security provides a password protection tool for your organization. Keeper Security supports SSO for Managed Services Providers (MSP) to access Managed Services Center (MSC) without the need for a separate login. An SSO login validates usernames and passwords against your corporate user database that is protected by IDaaS. See https://www.keepersecurity.com/. You can protect access to Keeper Security by integrating Keeper Security with Identity as a Service. Once integrated, users can use single sign-on to log in to their Keeper Security account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.37 and Keeper Security 24.1.25. Other versions of Keeper Security may require integration and configuration steps that differ from those documented in this procedure. For other versions of Keeper Security, this integration guide may be used as an initial approach for integrating Keeper Security. In the event of other issues, contact support@entrust.com for assistance.
Before you begin, open two browser windows. In one window, log in to your Keeper Security administrator account. In the other window, log in to your IDaaS administrator account.
Log in to your Keeper Security administrator account. The Keeper page appears.
Click Admin Console. The Getting Started page appears.
Click Admin. The Node set up page appears.
Under
Node, click
and select Add
Node. The Add Node
dialog box appears.
Enter a Name for the Node, for example, IDaaS.
Click Add Node.
Click Roles. The Roles page appears.
Configure a User with a role with the required enforcement policies, if one does not already exist.
Click the Provisioning tab. The User Provisioning page appears.
Click Add Method. The Select Provisioning Method page appears.
From the Node drop-down list, select the Node you created in Step 6, above.
Select Single Sign-On with SSO Connect On-Prem.
Click Next. The Single Sign-On with SSO Connect On-Prem page appears.
Enter the Enterprise Domain Name. For example, mycompany.us.trustedauth.com.
Click Next to create the provisioning method. Your node appears under Single Sign-On with SSO Connect Cloud with a status of Active.
Click
next to your Node and select
View.
Click Export Metadata and save the metadata to use in Step 2: Configure Security Keeper for Identity as a Service.
Click <-- (back) to return to the Single Sign-On with SSO Connect Cloud page.
Leave this page open to return to in a later step.
In Identity as a Service, click
> Security > Applications. The Applications Lists page appears.
Click Add. The Select an Application Template page appears.
Do one of the following:
Select SAML Cloud Integrations from the search drop-down list and scroll to find the application you want to add to IDaaS.
- or -
In the Search bar, enter a search option to filter for the application you want to add to IDaaS.
Click Security Keeper. The Add Keeper Security page appears.
Enter an Application Name.
Enter an Application Description.
Optional. Add a custom application logo.
Click
next to Application Logo. The Upload Logo dialog box appears.
Click
to select an image file to upload.
Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
If required, resize your image.
Click OK.
Select the Authentication Flow that appears to users during login.
Click Next. The General page appears.
Click Upload Metadata XML and browse to upload the metadata file you downloaded in Step 1: Configure Keeper Security for single sign-on for IDaaS.
Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
From the SAML NameID Attribute drop-down list, select Email.
From the SAML NameID Encoding Format drop-down list, select Email.
From the SAML Signing Algorithm drop-down list, select SHA512.
From the SAML Signing Certificate from the drop-down list, select the SAML Signing Certificate.
Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
Deselect Enable Go Back Button if you do not want users to be able to go back to the Security Keeper login page to log in.
Add three SAML Attributes, as follows:
Add the first name attribute, as follows:
Click Add. The Add Attribute dialog box appears.
In the Name field, enter First.
In the Value field, type <f and select First Name.
Click Add to return to the Add Application page.
Add the Last Name attribute, as follows:
Under SAML Attributes, click Add.
In the Name field, enter Last.
In the Value field, <l and select Last Name.
Click Add to return to Add Application page.
Add the Email attribute, as follows:
Under SAML Attributes, click Add.
In the Name field, enter Email.
In the Value field, <e and select Email.
Click Add to return to Add Application page.
Leave the remaining settings at the default values.
Click Submit.
Download the Metadata file from Identity as a Service
In Identity as a Service, click
> Security > Applications. The Applications List page appears.
Do one of the following:
Click
next to the application you are integrating with Identity as a Service.
–or–
Click
next to the application you are integrating with Identity as a Service and select SAML IDP Metadata.
The SAML Application Metadata dialog box appears.
Select the certificate to include in the SAML IDP Metadata file from the drop-down list.
If applicable, Select the domain to include in the SAML IDP Metadata file from the drop-down list.
Enter the Lifetime, in days, for the SAML IDP Metadata file. The value must be between 2 and 730.
Do one of the following, as required:
Copy the Public Endpoint to paste into your SAML application being used Identity Provider authentication.
Click Download.
Note: If you are using multiple domains, you must download each domain's metadata file separately because the values in the metadata file vary for each domain.
Return to the page you left open in Step 1: Configure single sign-on in Keeper Security for IDaaS.
Click
next to your Node and select
Edit.
The Identity Provider
page appears.
Scroll to SAML Metadata.
Upload the metadata file your downloaded from IDaaS in Step 4: Download the metadata file from Identity as a Service.
Click
Save.
Testing Service Provider Login
Open a Web browser and enter the URL https://login.Keeper Security.com/login. You are directed to Identity as a Service.
Enter your Keeper Security account User ID and click Next.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to the Keeper Security Console Home page.
Testing Identity as a Service redirect log in
Log in to your Identity as a Service account.
Go to your My Profile page if you are not already there.
Under Applications, click Keeper Security SAML.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to Keeper Security Console Home page.