Transitioning to Company-Specific URLs in RSA Authentication Manager (AM)
a year ago

Summary

To ensure compatibility with modern authentication methods, RSA Authentication Manager (AM) must be reconnected to RSA Cloud Authentication Service (CAS) to obtain company-specific URLs.

 

Applies To: Hybrid Cloud Deployment (between AM and CAS)

 

Details

Starting in March 2025, CAS will no longer support non-company-specific URLs such as https://access.securid.com and https://na2.access.securid.com. Continued use of these URLs may result in functionality disruptions.

 

To prevent this, RSA recommends that all customers who have integrated AM with CAS reconnect and obtain their company-specific URLs or upgrade to AM 8.7 SP2 Patch 5 or later. This transition ensures all authentication and configurations use secure, company-specific URLs, enabling modern authentication techniques.

 

Recommendation

To ensure uninterrupted access to the enhanced authentication features, follow the recommendations below:

  1. AM 8.7 SP2 Patch 5: Upgrading to AM 8.7 SP2 Patch 5 or later will automatically attempt to transition to the new company-specific URLs. If the transition fails due to communication issues with CAS, a warning will appear in the AM Security Console. Administrators must then manually reconnect AM to CAS to establish the connection.
  2. For AM 8.7 SP2 Patch 4 or Earlier Versions: Administrators must manually reconnect AM to CAS to obtain the company-specific URLs.
  3. For Restorations Using Backups of AM 8.7 SP2 Patch 4 or Earlier: Restoring a backup containing non-company-specific URLs requires reconnecting AM to CAS to acquire the new company-specific URLs.

For information on connecting to CAS, please refer to Quick Setup Guide - Connect Authentication Manager to Cloud Authentication Service.

Announcement