Step
1: Configure single sign-on in Keeper Security for IDaaSKeeper 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 user names 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.
Step
1: Configure single sign-on in Keeper Security for IDaaS1. Log in to your Keeper Security administrator account. The Keeper page appears.
2. Click Admin Console. The Getting Started page appears.
3. Click Admin. The Node set up page appears.
4. Under
Node, click 
and select Add
Node. The Add Node
dialog box appears.
5. Enter a Name for the Node, for example, IDaaS.
6. Click Add Node.
7. Click Roles. The Roles page appears.
8. Configure a User with a role with the required enforcement policies, if one does not already exist.
9. Click the Provisioning tab. The User Provisioning page appears.
10. Click Add Method. The Select Provisioning Method page appears.
11. From the Node drop-down list, select the Node you created in Step 6, above.
12. Select Single Sign-On with SSO Connect On-Prem.
13. Click Next. The Single Sign-On with SSO Connect On-Prem page appears.
14. Enter the Enterprise Domain Name. For example, mycompany.us.trustedauth.com.
15. Click Next to create the provisioning method. Your node appears under Single Sign-On with SSO Connect Cloud with a status of Active.
16. Click
next to your Node and select
View.
17. Click Export Metadata and save the metadata to use in Step 2: Configure Security Keeper for Identity as a Service.
18. Click <-- (back) to return to the Single Sign-On with SSO Connect Cloud page.
19. Leave this page open to return to in a later step.
Step 2: Add
Keeper Security to Identity as a Service1. In Identity as a Service, click 
> Security > Applications.
The Applications Lists
page appears.
2. Click Add. The Select an Application Template page appears.
3. Under SAML Cloud Integrations, click Security Keeper. The Add Keeper Security page appears.
4. Enter an Application Name.
5. Enter an Application Description.
6. Optional. Add a custom application logo.
a. Click 
next to Application Logo. The
Upload Logo dialog box appears.
b. Click 
to
select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
d. If required, resize your image.
e. Click OK.
7. Select the Authentication Flow that appears to users during login.
8. Click Next. The General page appears.
9. 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.
10. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
11. 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.
12. From the SAML NameID Attribute drop-down list, select Email.
13. From the SAML NameID Encoding Format drop-down list, select Email.
14. From the SAML Signing Algorithm drop-down list, select SHA512.
15. From the SAML Signing Certificate from the drop-down list, select the SAML Signing Certificate.
16. 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.
17. 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.
18. Add three SAML Attributes, as follows:
Add the first name attribute, as follows:
a. Click Add. The Add Attribute dialog box appears.
b. In the Name field, enter First.
c. In the Value field, type <f and select First Name.
d. Click Add to return to the Add Application page.
Add the Last Name attribute, as follows:
a. Under SAML Attributes, click Add.
b. In the Name field, enter Last.
c. In the Value field, <l and select Last Name.
d. Click Add to return to Add Application page.
Add the Email attribute, as follows:
a. Under SAML Attributes, click Add.
b. In the Name field, enter Email.
c. In the Value field, <e and select Email.
d. Click Add to return to Add Application page.
19. Leave the remaining settings at the default values.
20. Click Submit.
Step 3: Create
a resource rule to protect access to Keeper SecurityCreate a resource rule to protect access to a SAML application
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
6. Click Next. The Authentication Conditions Settings page appears.
7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.
8. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
13. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
14. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:
a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.
The risk score is based on the attribute differences
between a user's Machine Authentication information and that recorded
on Identity as a Service before the condition fails. If an attribute does
not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The
Non-Matching Risk Points values of each non-matching
attribute are added together, resulting in a total risk score. This score
is normalized to be out of 100 as follows:
Total Risk Score = (Total Risk Points
of Failing Attributes / Maximum Risk Points of All Enabled Attributes)
* 100
The resource rule condition fails when the number of non-matching risk
points exceeds the Machine Authentication Risk value defined in this step.
A value of 0 means that a single attribute
difference causes the Device Fingerprint
condition to fail. The default value is 3.
The value between 0-50 can be entered.
The default value is defined by the Machine Risk Limit.
See Modify machine authenticator settings.
b. Click Save.
17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.
19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
22. Click Submit to create the resource rule.
Step 4: Download
the metadata file from Identity as a ServiceDownload the Metadata file from Identity as a Service
1. In Identity as a Service, click
> Security > Applications.
The Applications List page appears.
2. 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.
3. Select the certificate to include in the SAML IDP Metadata file from the drop-down list.
4. If applicable, Select the domain to include in the SAML IDP Metadata file from the drop-down list.
5. Enter the Lifetime, in days, for the SAML IDP Metadata file. The value must be between 2 and 730.
6. Do one of the following, as required:
a. Copy the Public Endpoint to paste into your SAML application being used Identity Provider authentication.
b. 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.
Step 5: Upload
the metadata file from Identity as a Service1. Return to the page you left open in Step 1: Configure single sign-on in Keeper Security for IDaaS.
2. Click
next to your Node and select
Edit.
The Identity Provider
page appears.
3. Scroll to SAML Metadata.
4. Upload the metadata file your downloaded from IDaaS in Step 4: Download the metadata file from Identity as a Service.
5. Click Save.
Step 6: Test
the integrationTesting Service Provider Login
1. Open a Web browser and enter the URL https://login.Keeper Security.com/login. You are directed to Identity as a Service.
2. Enter your Keeper Security account User ID and click Next.
3. 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
1. Log in to your Identity as a Service account.
2. Go to your My Profile page if you are not already there.
3. Under Applications, click Keeper Security SAML.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to Keeper Security Console Home page.