Authentication Guide
Authentication Guide
Authentication Guide
CORPORATE H EADQUARTERS
5090 N. 40th Street
Phoenix, AZ 85018
Phone: 1 818-575-4000
COPYRIGHT NOTICE
Copyright © 2017 BeyondTrust Software, Inc. All rights reserved.
The information contained in this document is subject to change without notice.
No part of this document may be photocopied, reproduced or copied or translated in any manner to another
language without the prior written consent of BeyondTrust Software.
BeyondTrust Software is not liable for errors contained herein or for any direct, indirect, special, incidental or
consequential damages, including lost profit or lost data, whether based on warranty, contract, tort, or any other
legal theory in connection with the furnishing, performance, or use of this material.
All brand names and product names used in this document are trademarks, registered trademarks, or trade names
of their respective holders. BeyondTrust Software is not associated with any other vendors or products mentioned
in this document.
Contents
Contents
Introduction 5
Documentation for BeyondInsight 5
Contacting Support 5
Configuring Authentication 56
Troubleshooting 60
Introduction
This guide provides detailed instructions and procedures for using BeyondInsight.
This section includes the document conventions, list of documentation for the product, and where to get additional
product information.
Contacting Support
For support, go to our Customer Portal then follow the link to the product you need assistance with.
The Customer Portal contains information regarding contacting Technical Support by telephone and chat, along
with product downloads, product installers, license management, account, latest product releases, product
documentation, webcasts and product demos.
Telephone
Privileged Account Management Support
Within Continental United States: 800.234.9072
Outside Continental United States: 818.575.4040
Online
http://www.beyondtrust.com/Resources/Support/
Retina CS authentication provides native Retina CS authentication with users who are managed exclusively by
Retina CS. You can also add Active Directory users or groups and apply Retina CS authentication.
To allow a user to log in using Retina CS authentication, the user account must reside in the Retina CS database.
5. Select the Use SSL check box to use a secure connection when accessing Active Directory. You must turn on
SSL authentication in the Configuration tool. See Using SSL for Active Directory Queries.
6. Click Credentials.
a. Click Add.
b. Enter the credential for the domain or DC.
c. Click Test to ensure the credential can successfully authenticate with the domain or DC.
d. Click OK.
7. After you enter domain or DC and credential information, click Search.
A list of Security Groups in the selected domain is displayed.
For performance reasons, a maximum of 250 groups from Active Directory is retrieved. The default filter is an
asterisk (*) which is a wildcard filter that returns all groups. Use the group filter to refine the list.
8. Set a filter on the groups that will be retrieved. (Optional).
Example filters:
a* (returns all group names that start with a)
*d (returns all group names that end with d)
*sql* (returns all groups that contain 'sql' in the name)
9. Click OK.
10. Enter a name and description for the user group.
11. Select the Active check box to activate the user group. Otherwise, clear the check box and activate later.
12. Select the permissions and access levels.
13. Select the Smart Rules and access levels to the rules.
14. Click Create.
Access Levels
Mapping to
Outgoing Claim Type Outgoing Claim Type BeyondInsight
User Detail
Group
http://schemas.xmlsoap.org/claims/Group Required
membership
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name Required User name
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname Optional Surname
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname Optional First name
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress Optional Email address
3. Click Next.
4. Select Using an existing STS.
5. Enter Root URL of Claims Issuer or STS ( https://adfsaccount.adatum.com )
7. Click Next.
8. Select a STS signing certificate option, and then click Next.
9. Select an encryption option, and then click Next.
10. Select the appropriate claims, and then click Next.
11. Review the settings on the Summary page, and then click Finish.
16. Copy the signing certificate to BeyondInsight server and save it in this location:
C:\Program Files (x86)\eEye Digital Security\Retina CS\WebSiteSAML\Certificates
17. Rename the certificate to: “pingone.cer”
18. Copy private certificate with key to:
C:\Program Files (x86)\eEye Digital Security\Retina CS\WebSiteSAML\Certificates
19. Open the saml.config file:
C:\Program Files (x86)\eEye Digital Security\Retina CS\WebSiteSAML\saml.config
20. In Notepad,
– edit the ServiceProvider Name:
https://ServerURL/eEye.RetinaCSSAML
14. Select appropriate settings for okta support and click Finish.
16. Copy the Identity Provider Single Sign-On URL. Save the value to be used in step 21.
17. Copy the Identity Provider Issuer. Save the value to be used in next step 21.
18. Click Download Certificate and save this on the BeyondInsight server in
C:\Program Files (x86)\eEye Digital Security\Retina CS\WebSiteSAML\Certificates
19. Rename the certificate to “okta.cer”.
Self-Signed Certificates
On the UVM, self-signed certificates were created for Client Authentication and Server Authentication during
configuration. These certificates were placed in the Personal Certificates Store, and will show as “Issued By”
eEyeEmsCA.
However, to authenticate using Smart Cards, BeyondInsight will need to use a WebServer certificate that was
issued from the local Certificate Authority (CA).
To view the self-signed certificates:
1. Remote Desktop to the UVM.
2. Log on using the username and password that was created during the configuration of the UVM.
3. Once logged on, open MMC and add the Certificates Snap-in for the Local Computer account.
4. Under Certificates (Local Computer) you can browse to Personal > Certificates to view the current certificates.
WebServer Certificate
You must replace the self-signed certificate with a domain certificate. Because the UVM is not part of your domain,
you need to Create a Certificate Request and get it to the local CA manually.
c. Enter a File Name. Browse to where you would like the file placed.
d. Click Finish.
6. The file created, when opened, should look something like this:
4. When the command is executed, you will be prompted to select a CA from the Certification Authority List to
send the request to. This will be the CA that will issue the certificate.
5. Enter a name for the newly issued certificate, and select a file location.
4. Browse to locate the certification authority’s response, and give it a Friendly name.
5. The certificate has been added to the Server Certificates in IIS, and in the Personal Certificates Store of the
UVM.
However, the self-signed cert must be replaced.
4. At the bottom you will see the currently assigned SSL certificate. Either click the Select button and then select
the Domain Issued certificate and click OK, or use the dropdown menu.
5. Click Close on the Site Bindings dialog box. At this time, you can exit out of IIS.
Export Subordinate CA
If you have a Subordinate CA, you will need to export that also.
1. To get the Subordinate CA’s certificate, go to Intermediate Certification Authorities > Certificates.
2. Right-click the Subordinate CA, then select All Tasks > Export.
Now the Root and Subordinate CA certificates need to be imported to Intermediate Certification Authorities >
Certificates store using the same method as above.
5. Make sure you are placing the certificates in the right store.
Troubleshooting
If you receive a 403 Forbidden error like the one below, more than likely this has to do with your CRL Distribution
Points (CDP).
Even though the certificate is trusted, Password Safe has to be able to verify that your user certificate is not on the
Certificate Revocation List. By default, a copy of the CRL and the Delta CRL are kept in Active Directory, locally on
the CA, and usually on a file share. However, none of those options will work because the UVM is not joined to a
domain. In order for the UVM to successfully download the CRL and Delta CRL, an http CDP will have to be
configured.
The easiest way to accomplish this is to enable Directory Browsing for the CertEnroll Virtual Directory in IIS on the
CA. If the virtual directory is not present, you can create one.
1. Open IIS on the Subordinate CA.
2. Navigate to the CertEnroll Virtual Directory.
5. Now you must create the CDP. To do this open mmc, and add the Certificate Authority snap-in.
6. Right-click the CA server name, and select Properties.
7. Select the Extensions tab.
8. Click Add and create http CDP. It should look something like this:
http://<ServerDNSName>/CertEnroll/<CaName><CRLNameSuffix><DeltaCRLAllowed>.crl
9. Ensure the following check boxes are selected:
– Include in CRLs. Clients use this to find Delta CRL Locations
– Include in the CDP extension of issued certificates
Configuring Authentication
You can use set up Smart Card authentication or two-factor authentication using a RADIUS server.
– Transmit NAS Identifiers - When the check box is selected, NAS identifiers are transmitted to permit
access. In some cases, a RADIUS server will not permit access if NAS identifiers are not transmitted.
In BeyondInsight, the attributes that are transmitted:
– NAS IP Address - This is the IP address where BeyondInsight is installed.
– NAS Identifier - This is the string BeyondInsight.
5. Click Create.
6. Click Update.
Troubleshooting