RSA Authenication Manager 8.2 Support for Authenticate Tokencodes

Document created by RSA Information Design and Development on Aug 18, 2017Last modified by RSA Information Design and Development on Sep 15, 2017
Version 2Show Document
  • View in full screen mode

You can configure RSA Authentication Manager to send Authenticate Tokencodes to the Cloud Authentication Service for authentication, allowing users of the RSA SecurID Authenticate app to access traditional on-premises resources, like VPNs and wireless access points protected by Authentication Manager.

To download complete integration instructions, see Integrating the Cloud Authentication Service and RSA Authentication Manager on RSA Link at https://community.rsa.com/docs/DOC-53954.

RSA Authentication Manager 8.2 support for Authenticate Tokencodes requires the following:

  • You must add RSA SecurID Access (Cloud Authentication Service) to Authentication Manager as a trusted realm.
  • Users who are using both SecurID and Authenticate Tokencode must be configured with different database attributes for each form of authentication. For example, you can use the SAMAccountName attribute for SecurID authentication and an e-mail attribute for the Authenticate Tokencode. In this case, users can use both SecurID and Authenticate Tokencode if they remember to use the correct username or e-mail address required to access each protected resource.

For more information on RSA Authentication Manager 8.2, see the RSA Authentication Manager 8.2 Administrator's Guide on RSA Link at https://community.rsa.com/community/products/securid/authentication-manager-82.

 

 

You are here
Table of Contents > RSA Authentication Manager Integration > RSA Authenication Manager 8.2 Support for Authenticate Tokencodes

Attachments

    Outcomes