Cloud Authentication Service Quick Setup Guide for SAML Applications and Third-Party SSO Solutions

[#1]

This guide helps you quickly set up your production deployment for the Cloud Authentication Service and add authentication for a SAML 2.0 application, third-party SSO solution, or Microsoft Azure Active Directory. Use this guide with the Planning Guide. If you have completed a deployment with another Quick Setup Guide and want to set up the deployment described in this guide, skip the steps that you have already completed.

Step 1: Plan

Step 2: Deploy the Identity Router

Step 3: Connect LDAP Directory

Step 4: Add an Access Policy

Step 5: Enable My Page

Step 6: Protect a Resource

Step 7: Test

Note:  If you are deploying an identity router that is embedded in RSA Authentication Manager 8.5 or later, see Configure an Embedded Identity Router for instructions.

​Step 1: Plan

There are a few things you need to plan to deploy your system.

What You Need to Have

Item	Description
Sign-in credentials to the Cloud Administration Console	Sign-in credentials are emailed to you after you request an environment from RSA Sales or your partner or complete the trial form. Be sure that the email address that you provide to RSA is for a real user in your LDAP directory and not, for example, a group alias or general account. For browser requirements, see Supported Browsers for the Cloud Administration Console.
Virtual appliance infrastructure Required only for identity router deployment on-premises in a VMware or Hyper-V environment	Hardware requirements for image file: Disk space: 54 GB Memory: 8 GB Virtual CPUs: 4 Network interface: VMware: One E1000 virtual network adapter (two if using the SSO Agent) Microsoft Hyper-V: One synthetic network adapter (two if using the SSO Agent) For additional guidance, see Network Interface Requirements and Recommendations. Software requirements: VMware or VMware Platform: VMware ESXi 5.5 or later (currently 6.x series) VMware vSphere Client: Any version that works with the supported ESXi deployments Hyper-V 2012 R2
Amazon Web Services (AWS) account Required only for identity router deployment in an Amazon Web Services cloud environment Note:  To deploy an identity router in the Amazon cloud, you must be familiar with the following concepts as they relate to AWS: Elastic Compute Cloud (EC2) Amazon Machine Image (AMI) Elastic IP Address Security Groups Virtual Private Cloud (VPC) Subnets Route Tables Network Access Control Lists (ACL) DHCP Option Sets Internet Gateway NAT Gateway Virtual Private Gateway VPN Connection VPC Peering	Amazon Virtual Server Instance hardware requirements: Family: General purpose Type: t2.large vCPUs: 2 Memory: 8 GB AWS cloud environment requirements: Access to t2.large or better instance types Virtual Private Cloud with private and public subnets Route Tables, Security Groups, and Network ACLs that allow traffic between the identity router and all other components in your deployment DHCP Option Sets that specify all DNS servers required for your deployment Elastic IP addresses (if your organization manages its own DNS service)
Microsoft Active Directory 2008 or 2012 or LDAPv3 directory server	Create a group of a limited number of users (for example, RSA SecurID Access Test Group) to synch and test with.
SSL/TLS certificate from your LDAP directory server	Used for an encrypted connection (LDAPS) to your directory server. Download the SSL/TLS certificate from your directory server. If your directory server does not have a certificate, install one. See Cloud Authentication Service Certificates.
A mobile device or Windows PC	iOS 11.0 or later Android 6.0 or later Windows 10 Version 1511 or later

What You Need to Know

RSA SecurID Access uses a hybrid architecture that consists of two components:

• The Cloud Authentication Service is a cloud service that provides an easy-to-use Cloud Administration Console and powerful identity assurance engine.

• The identity router is a virtual appliance that securely connects your on-premises resources, such as Active Directory, to the Cloud Authentication Service. You can deploy the identity router in your on-premises VMware or Hyper-V environment, or in the Amazon Web Services (AWS) cloud.

Note:  After an identity router is registered in a deployment, it cannot be reused in another deployment. For example, suppose you registered an identity router with Company A for a trial deployment, and you want to use the same identity router with Company A in a production deployment. You must add a new identity router (virtual machine) to the production deployment.

Planning Network Interfaces for the Identity Router

Relying party deployments support both standalone and embedded identity routers. For details on planning network interfaces, see Identity Router Network Interfaces and Default Ports.

In all deployments with AWS, the identity router has one network interface to which you assign public and private IP addresses and connect other network resources from the internet or your private network.

Planning Worksheet

Add your values to the following worksheet. You will use this information in the next section and during setup.

Item	Your Values
Cloud Administration Console and Cloud Authentication Service	US region:<authentication_service_domain>, *.access.securid.com, (52.188.41.46, 52.160.192.135). ANZ region:<authentication_service_domain>, *.access-anz.securid.com (20.37.53.30, 20.39.99.202) EMEA region: <authentication_service_domain>, *.access-eu.securid.com (51.105.164.237, 52.155.160.141) Your authentication service domain appears in the Cloud Administration Console on the Platform > Identity Router > Registration page when you add an identity router. For instructions on checking the status of your Cloud connections, see View Identity Router Status in the Cloud Administration Console. To test access to the IP addresses, see Test Access to Cloud Authentication Service.
LDAP directory server IP address FQDN Base DN of users (the root where users will be synchronized from, for example, DC=company, DC=com) Administrator account credentials that RSA SecurID Access can use to connect to the directory server
DNS servers IP addresses
NTP server IP address
Required only for VMware and Hyper-V identity router deployments:
Identity router management interface (private, required for all deployments) IP address Netmask Gateway Short hostname FQDN
Identity router portal interface (public, required for SSO Agent deployments with on-premises identity router) IP address Netmask Gateway Short hostname FQDN
Required only for Amazon Web Services identity router deployments:
Identity router Private IP Address (Used for communication with internal resources in the same VPC, another VPC, or your on-premises network.) Public Elastic IP Address (Used for communication with public resources over the internet if the identity router is in a public subnet. Not required if a NAT/load balancer with a public IP address manages traffic to the identity router.) Short hostname FQDN Note:  For identity routers in AWS, netmask and gateway information is obtained automatically during instance launch, according to the VPC subnet settings.
AWS environment configuration details VPC Private subnet Public subnet DHCP options set Route tables Security groups Network ACLs

Connectivity Requirements

Replace the values in the table below with your values from the table above. This table identifies the connectivity requirements that you might need to provide to your IT group to update firewall rules for your network. If you deploy the identity router in the Amazon cloud, the route tables, security groups, and network ACLs in your AWS environment must also allow these connections. Update your connectivity settings before continuing with the next step.

Source	Destination	Protocol and Port	Purpose
0.0.0.0/0	Both Cloud Authentication Service environments	TCP 443	External user access to Cloud Authentication Service
< Your administrators>	For on-premises identity routers: <Your identity router management interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	On-premises (two network interfaces): TCP 443 One network interface or Amazon: TCP 9786	Identity Router Setup Console
For on-premises identity routers (one network interface): <Your identity router management interface IP address> For on-premises identity routers (two network interfaces): <Your identity router portal interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	Cloud Administration Console and both Cloud Authentication Service environments Note:  If your company uses URL filtering, be sure that *.access.securid.com, *.auth.securid.com, and the Cloud Authentication Service IP addresses for your region are whitelisted. Also, confirm that you can access both environments. For instructions, see Test Access to Cloud Authentication Service.	TCP 443	Identity router registration
For on-premises identity routers: <Your identity router management interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	<Your LDAP directory server IP address>	TCP 636	LDAP directory user authentication and authorization
For on-premises identity routers: <Your identity router portal interface IP address or identity router management interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	<Your DNS server IP address>	UDP 53	DNS
For on-premises identity routers: <Your identity router portal interface IP address or identity router management interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	<Your NTP server IP address>	UDP 123	Network time server synchronization
<Your administrator computer>	For on-premises identity routers: <Your identity router management interface IP address> For identity routers in the Amazon cloud: <Your identity router private IP address>	TCP 22	(Optional) SSH for troubleshooting See Access SSH for Identity Router Troubleshooting.

​Step 2: Deploy the Identity Router

Perform these steps to set up an identity router quickly using only required settings. If you want to use advanced configuration options, see Deploying an Identity Router - Advanced Setup.

Add an Identity Router

Procedure 

1. Sign into the Cloud Administration Console using the URL and credentials that RSA emailed to you.
2. Click Platform > Identity Routers.

3. On the Identity Routers page, click Add an Identity Router, and follow the instructions.

   Under Registration Details, copy the Registration Code and Authentication Service Domain to a location where you can access them later on.

   

4. Click Close.

Install or Create the Identity Router Virtual Appliance or Machine

You can install the virtual appliance image using a VMware administration client such as vSphere, by either connecting to the VMware vCenter Server, or connecting directly to the VMware ESXi host.

Or you can use Hyper-V Manager or Amazon Web Services EC2 to create a virtual machine for the identity router.

Procedure 

1. In the Cloud Administration Console, click Platform > Identity Routers.
2. Click Download Identity Router Image and do one of the following:
   • For VMware, click Download OVA Image for VMware, and save the image to a location accessible by VMware.
   • For Hyper-V, click Download VHD Image for Hyper-V, and save the image to a location accessible by Hyper-V.
   • For Amazon Web Services:
     1. Click Access AMI Image for Amazon.
     2. Enter your AWS Account ID.
     3. Click Update AMI Access.
     4. Note the values in the Identity Router AMI Name and AWS Regions with AMI Access fields. You can search the AWS private images catalog using these values to quickly locate the AMI.

3. Do one of the following:

   • To use VMware, sign into the VMware client, do the following:

     1. Follow the VMware client documentation to install the virtual appliance from the image. When prompted, enter the following data:

        • Name to use for the virtual appliance
        • VMware host or cluster for the virtual appliance
        • Resource pool for the virtual appliance
        • Storage location or data store to use for the virtual appliance
        • Format for storing virtual disks
        • Networks to be used for the virtual appliance

     2. If you are deploying the identity router with a single network interface, then delete the second network interface.

     3. Power on the virtual machine.

   • To use Hyper-V Manager, sign into Hyper-V Manager, and do the following:

     1. Click Hyper-V Host > New > Virtual Machine.

     2. Follow the wizard. In each dialog box, provide the following information.

        Dialog Box	Required Information
        Specify Name and Location	Name of the identity router virtual machine.
        Specify Generation	Select Generation 1.
        Assign Memory	Startup memory = 8192 MB (recommended).
        Configure Networking	Select the network for the management network adaptor.
        Connect Virtual Hard Disk	Select Use an existing virtual hard disk and browse to the location where the identity router VHD image is available.
        Completing the New Virtual Machine Wizard	Review and click Finish.

     3. Perform these steps only for deployments with two network interfaces:

        • To configure the second network, select the new virtual machine, right-click, and select Settings .

        • On the Add Hardware page, select Network Adapter and click Add.

        • Select the network for your portal interface, then click Apply and OK.

     4. Select the new virtual machine from the list of virtual machines. Right-click and select Start.

     5. With the virtual machine selected, right-click again and select Connect.

   • To use Amazon Web Services, sign into Amazon EC2 and follow the documentation provided by Amazon to do the following:
     1. Make sure your AWS environment includes a VPC which meets the following requirements:
        • Private and public subnets are configured according to your deployment requirements.
        • Route tables, security groups, and network ACLs are configured to allow necessary traffic to and from the other network resources in your deployment, such as users and identity sources.
        • All DNS servers required for your deployment are specified in the DHCP options set.
     2. Launch the virtual instance using the AMI.
        When prompted, specify the following:

     Setting	Description
     AMI template	The AMI template image provided by RSA.
     Instance type	Determines presets for the virtual instance. The identity router requires a t2.large instance or greater.
     Virtual Private Cloud (VPC)	The section of your Amazon environment where you will deploy the identity router.
     Subnet	A subnetwork within your VPC where you will deploy the identity router. The subnet can be either public or private, depending on how resources and users will connect to the identity router.
     Auto-assign Public IP	Determines whether Amazon issues dynamic public IP addresses for the identity router, or the IP address is determined by the subnet settings. If your organization manages its own DNS service, RSA recommends allocating a persistent Elastic IP address through Amazon Web Services, and assigning it to the identity router instance after you complete the launch process.
     Storage	Virtual storage space. The identity router requires 54 GB General Purpose SSD (GP2) storage.
     Tags	Optional labels that describe this identity router. RSA recommends adding a tag specifying the Fully Qualified Domain Name, which acts as a unique identifier to differentiate this identity router from others in your deployment.
     Security groups	Firewall rules that control traffic to and from the identity router. Add security groups that allow necessary traffic from other network resources according to your deployment model.

     3. Review the configuration and launch the instance.
     4. If prompted to select a key pair, select Proceed without a keypair.
     5. Use the Get instance screenshot feature to monitor instance deployment status. When deployment is complete, refresh the screenshot and write down the URL displayed for the Identity Router Setup Console.

Configure Initial Network Settings Using the Identity Router VM Console

You use the Identity Router VM Console to configure IP addresses and static routes for on-premises identity routers deployed in your VMware or Hyper-V environment.

Note:  This procedure is not required for identity routers in the Amazon Web Services cloud.

Procedure 

1. Connect to the identity router using your VMware or Hyper-V management client.
2. Sign into the Identity Router VM Console:

   Username: idradmin

   Password: s1mp13

   You are prompted to change these credentials the first time you sign in.

3. Refer to the planning worksheet for the values to complete the Management sections.

   Use the Up and Down arrows to navigate the main menu. Press Enter to select a menu option or configure its settings. Use Tab and Shift + Tab to navigate between settings and back to the main menu. When the cursor is in the settings panel, press F10 to save or Esc to revert. Press F10 after you complete each section to save your values.

4. Select Commit in the left-hand frame to save the network configuration settings.

5. Write down the URL that appears.

   

Connect Identity Router to Cloud Administration Console

Procedure 

1. Open a web browser and go to the URL that you wrote down in the previous section.

2. Sign into the Identity Router Setup Console:

   Username: idradmin

   Password: s1mp13

   You are prompted to change these credentials the first time you sign in.

3. Add any DNS servers that you did not add in the Identity Router VM Console.
   

   Note:  These DNS server settings do not apply for identity routers in the Amazon cloud. Edit the DHCP option set in your Amazon Web Services environment if you need to add DNS servers for an Amazon cloud-based identity router.

4. If you enabled two network interfaces in the Identity Router VM Console, update the IDR Portal Interface Information section with appropriate details.

5. Click Update IDR Setup Configuration.

6. Click Connect Administration Console.

7. In the Registration Code field, enter the Registration Code displayed when you added the identity router in the Cloud Administration Console.

8. In the Authentication Service Domain field, enter the Authentication Service Domain displayed when you added the identity router in the Cloud Administration Console.

9. Click Submit.

   A confirmation message appears when the identity router is connected to the Cloud Administration Console. Also, note that the Identity Router Setup Console contains other pages that provide network diagnostics and detailed logs for the identity router.

10. Sign into the Cloud Administration Console to check the status of the identity router (Platform > Identity Routers).

    When the identity router is connected to the Cloud Administration Console, the status reads Active. This process usually takes up to five minutes.

11. In the Cloud Administration Console, click Publish Changes to apply the configuration settings for the new identity router.

    

​Step 3: Connect LDAP Directory

Add a Connection to LDAP Directory

Perform these steps to connect to an LDAP directory quickly using only required settings. If you want to use advanced options, see Add an Identity Source.

Procedure 

1. In the Cloud Administration Console, click Users > Identity Sources.
2. Click Add an Identity Source > Select next to the directory to add.
3. Enter the identity source name and root (the base DN for users from the planning worksheet).
4. In the SSL/TLS Certificate section, unselect Use SSL/TLS encryption to connect to the directory servers.
5. In the SSL/TLS Certificates section:
   1. Select Use SSL/TLS encryption to connect to the directory servers.
   2. Click Add and select the SSL/TLS certificate.
6. In the Directory Servers section, add each directory server in the identity source, and test the connection.
7. Click Next Step.
8. On the User Attributes page, click Refresh Attributes, and verify that a valid list of attributes appears.

9. Select Use selected policy attributes with the Cloud Authentication Service.

   

10. In the Policies column, select sAMAccountName, virtualGroups, and memberOf or other attributes that you might use to identify users.

    

11. Click Next Step.

12. In the User Search Filter field, specify your test group using a filter. The following is an Active Directory example:

    (&(objectCategory=Person)(sAMAccountName=*)(objectClass=user)(mail=*)(memberOf=<yourgroup_distinguishedName>))

    Where <yourgroup_distinguishedName> is the name of your test administrator group.

    For example, (&(objectCategory=Person)(sAMAccountName=*)(objectClass=user)(mail=*)(memberOf=CN=SecurIDAccessUsers,OU=Groups,DC=Corp,DC=local))

13. Click Save and Finish.
14. Click Publish Changes.

Synchronize LDAP Directory for the Cloud Authentication Service

Synchronize data between the Cloud Authentication Service and your LDAP directory to ensure that the Cloud Authentication Service reflects any updates made to the LDAP directory.

During synchronization, users are added and attribute values that you selected in the previous step are copied to the Cloud Authentication Service. User passwords are not synchronized.

Procedure 

1. In the Cloud Administration Console, click Users > Identity Sources.
2. Next to your identity source, select Synchronization from the drop-down menu.

3. In the Identity Source Details section, click Synchronize Now.

   Depending on the number of users you are synching, this process can take a number of minutes.

​Step 4: Add an Access Policy

Create an access policy that you will assign to RSA SecurID Access My Page (a web portal used for authenticator registration) when you configure it. For simplicity, this access policy will not require additional authentication of users. You can change this policy in the future.

Perform these steps to add a policy using only required settings. If you want to set up a more complex policy, see Add an Access Policy.

Procedure 

1. Sign in to the Cloud Administration Console.
2. Click Access > Policies.
3. Click Add a Policy.
4. Enter the name (for example, No Additional Authentication), and select the identity source.

5. On the Rule Sets page, do the following:

   1. In Apply to, select All Users.
   2. In the Access, specify Allowed.
   3. In Additional Authentication, select Not Required.

   

6. Click Save and Finish.

7. Click Publish Changes.

​Step 5: Enable My Page

RSA SecurID Access My Page is a web portal that helps provide a secure way for users to complete authenticator registration. Perform these steps to enable My Page for your company. If you want to configure advanced settings for My Page, see Manage My Page.

Procedure 

1. In the Cloud Administration Console, click Platform > My Page.

2. Enable My Page.

3. Write down your My Page URL.

4. In the Primary Authentication Method drop-down list, select the authentication method to use.

5. In the Access Policy for Additional Authentication drop-down list, select the No Additional Authentication policy that you created earlier.

6. Click Save.

​Step 6: Protect a Resource

Configure a SAML 2.0 application or third-party SSO solution to be protected by RSA SecurID Access. In the configuration wizard, select the preconfigured policy All Users Low Assurance Level as the access policy.

For example, you can protect Workday, ServiceNow, and Microsoft Office 365. For instructions, see the following:

• Workday - RSA SecurID Access Implementation Guide

• ServiceNow - RSA SecurID Access SAML Implementation Guide

• Microsoft Office 365 - RSA SecurID Access Cloud IdP/ Relying Party Implementation Guide

For instructions for all supported applications, see the RSA SecurID Access category on RSA Ready.

​Step 7: Test

Register a Device with the RSA SecurID Authenticate App

Perform these steps to quickly register a device. For additional information, see Registering Devices with RSA SecurID Authenticate App.

Procedure 

1. On one device (for example, your computer), do the following:

   1. Go to RSA SecurID Access My Page.

   2. Enter your email address.

   3. Enter your RSA SecurID passcode or password, depending on what you configured.

   4. Complete any additional authentication that you are prompted for.

   5. Click RSA SecurID Authenticate app >Get Started.

2. On another device ( iOS, Android, or Windows 10 ), download the RSA SecurID Authenticate app:

   • iOS: Apple App Store
   • Android: Google Play
   • Windows 10: Microsoft Store

3. On your computer, on the Registration page, click Next.

4. On your mobile device, do the following:

   1. Open the RSA SecurID Authenticate app.

   2. Tap Allow to allow the Authenticate app to send notifications.

   3. Allow or deny Google Analytics data collection. You can select either option to use the Authenticate app.

   4. Accept the license agreement.

   5. Tap Scan QR Code.

   6. Allow the app to access your camera.

   7. Scan the QR code that displays in My Page.

   8. Tap OK after setup is complete.

   9. Swipe through the tutorial.

   10. The app home screen appears, and the app is ready for use.

       

5. On your computer, on the Registration page, click Test Now.

6. RSA SecurID Access sends a notification to your registered device.

7. On your mobile device, tap the notification and approve it.

8. The My Page home screen displays. You have successfully registered and tested your device.

Sign Into the Protected Resource

Procedure 

1. Start the sign-in process to the protected resource.

   RSA SecurID Access sends a notification to your phone.

2. Tap Approve on your mobile device.

3. Select Remember this browser, and click Continue.

   You are signed into the resource.

You are here

Quick Setup Guide RP HTML