Add an Identity Router Using the Cloud Administration Console

Document created by RSA Information Design and Development on Jul 14, 2016Last modified by RSA Information Design and Development on Sep 15, 2017
Version 17Show Document
  • View in full screen mode
  

Before installing an identity router virtual appliance, you must add an identity router record to the Cloud Authentication Service using the Cloud Administration Console. When performing this task, you obtain a unique Registration Code, which is required to connect the identity router virtual appliance to the Cloud Administration Console.

Procedure 

 
  1. Sign into the Cloud Administration Console.
  2. Click Platform > Identity Routers.
  3. On the Identity Routers page, click Add an Identity Router.
  4. In the Name field, enter the Identity Router Proxy Interface FQDN value for this identity router from the RSA SecurID Access Solution Architecture Workbook.
    Using the FQDN guarantees that each identity router record has a unique name, and acts as a simple method to identify the corresponding identity router appliance on your network. If your company deploys FIDO Tokens and you change the FQDN after you add the identity router, all users who previously registered their tokens must register again.
  5. (Optional) In the Description field, describe this identity router.
    Include the IP address and domain name of the identity router in the description field so that you can identify the corresponding identity router appliance on your network.
  6. In the Portal Hostname field, enter the Identity Router Proxy Interface FQDN value for this identity router from the RSA SecurID Access Solution Architecture Workbook.
    This value must match the hostname you specify when you install and configure the identity router virtual appliance. The hostname must be within the protected domain for your network environment, and must be configured in your DNS server to point to the identity router proxy IP address.

    For more information, see Identity Router DNS Requirements.

  7. From the Cluster drop-down menu, select the cluster to which this identity router belongs.
    RSA SecurID Access creates a default cluster that you must select when you add the first identity router. You can edit and rename the default cluster after you deploy at least one identity router. If your deployment already has multiple clusters, refer to the diagram of your deployment in the RSA SecurID Access Solution Architecture Workbook to determine which cluster to select.
  8. From the Status drop-down menu, select Enabled.
  9. In the Timeout (seconds) field, specify the length of time the Cloud Authentication Service attempts to communicate with an unresponsive identity router before logging an error and updating the connection status indicator.
  10. Click Next Step.
  11. (Optional) Configure one or more firewall rules to allow connections from specific IP addresses to specific ports on the identity router. See the Connectivity Requirements section of the RSA SecurID Access Solution Architecture Workbook for the list of firewall rules required for your deployment.
    For example, you can add a firewall rule to allow a load balancer to access the identity router status servlet on port 8080.
     
    1. From the Connection Method drop-down menu, select the connection method to allow.
    2. From the Protocol drop-down menu, select the protocol to allow.
    3. In the Port Range/Message Type field, enter the port or port range to open for the connection.
    4. In the Source Network field, enter the network address/prefix pair for the source network where the allowed connections will originate.
    5. (Optional) Click ADD. Repeat steps a through d to add each firewall rule.
  12. (Optional) Configure one or more static routes if your company network requires the identity router to connect through specific network paths to access specific network resources. For example, you can add a static route to allow the identity router to access the Cloud Authentication Service through a specific gateway.
    Static routes are not required if all network resources are accessible through the default gateway connected to the identity router network interfaces.
     
    1. In the IP Address field, enter the IP address of the network resource.
    2. In the Network Mask field, enter the network mask of the network resource. For example, 255.255.255.0.
    3. In the Gateway field, enter the gateway address for the static route.
    4. From the Device drop-down menu, select the device type for the static route.
      The device type specifies whether the static route applies for connections to the proxy interface (Public) or the management interface (Private) of the identity router.
    5. (Optional) Click ADD. Repeat steps a through d to add each static route.
  13. (Optional) Configure one or more static DNS entries if you need to enable this identity router to resolve specific hostnames that are not provided by the DNS server.  
    1. In the IP Address field, enter the IP address for the static DNS entry.
    2. In the Aliases field, enter one or more hostname aliases for the static DNS entry, separated by a space.
    3. (Optional) Click ADD. Repeat steps a and b to add each static DNS entry.
  14. Click Save and Next Step.
  15. Under Registration Details, copy the Registration Code and Authentication Service Domain to a location where you can access them when you install and configure the identity router.
  16. Click Close.
 

After you finish 

Download the Identity Router Image.

 

 

You are here
Table of Contents > Identity Routers > Add an Identity Router Using the Administration Console

Attachments

    Outcomes