Configuring RSA SecurID (Cloud) For Omnissa Access

When the RSA SecurID authentication method is used, Omnissa Access is configured as the authentication agent in the RSA SecurID security console. RSA SecurID authentication requires users to authenticate with a token-based one-time passcode. RSA SecurID is a recommended authentication method for users accessing Omnissa Access from outside the enterprise network, where the risk of credential compromise is higher.

The RSA SecurID (cloud deployment) authentication method is a connector-based method. You must install the Omnissa Access connector and its User Auth service component. This method relies on the Omnissa Access connector to communicate directly with your RSA Authentication Manager server (the RSA SecurID server), rather than routing authentication through the cloud service.

When you configure SecurID to provide additional security, you must ensure that your network is properly configured for your Omnissa Access deployment. For SecurID specifically, you must ensure that the appropriate port is open to enable SecurID to authenticate users outside your network. If you deploy multiple RSA Authentication Manager server instances for redundancy, those instances must sit behind a load balancer that meets Omnissa Access networking requirements.

Configuring RSA SecurID with Omnissa Access is a three-part process:

1. Prepare the RSA Authentication Manager server: After you install the Omnissa Access connector and the User Auth Service, you add the connector as an authentication agent on the RSA Authentication Manager server.
2. Meet load balancer requirements (if applicable): If you have deployed multiple RSA Authentication Manager server instances, configure them behind a load balancer that meets the port and certificate requirements for the integration to work.
3. Configure the SecurID authentication method: After the RSA Authentication Manager server is prepared, you set up the SecurID authentication method in the Omnissa Access console Connector Authentication Methods page, using the host name, communication port, and access key from the RSA Authentication Manager instance.

After the authentication method is configured, associate it with the built-in identity provider and add it to an access policy rule so users are prompted for RSA SecurID authentication when they sign in.