Effective 25 August 2026, non-company-specific URLs will no longer be available. The following will no longer be supported:
- Logging in to the Cloud Administration Console using non-company-specific URLs (using password or third-party IdP)
- Access to the Cloud Administration APIs using non-company-specific URLs, including through Authentication Manager or any third-party REST API client
Action Required
Customers currently using non-company-specific URLs must:
- Transition to company-specific URLs immediately (Company-Specific Administrative URL Update Instructions).
- Verify that all integrations, scripts, and configurations no longer depend on non-company-specific URLs.
- Ensure that the necessary firewall rules are updated for tenant-specific endpoints.
Before the permanent shutdown, we will conduct temporary shutdowns of non-company-specific URLs across regions to help customers validate their configurations and ensure readiness. Continued use of non-company-specific URLs after 25 August 2026 will result in permanent shutdown of administrative service.
What to Expect
- During the temporary shutdown window, non-company-specific URLs (for example, https://na2.access.securid.com) will be unavailable in the respective region.
- Company-specific URLs (for example, https://<companyName>.access.securid.com) will remain fully operational and should be used instead.
- Customers still relying on non-company-specific URLs will experience disruption during the temporary shutdown window.
Temporary Shutdown Schedule
The following table provides the temporary shutdown schedule for shared URLs.
Note: During each region's 24-hour maintenance window, shared URLs will be unavailable for users in that region.
| Date | Region and Time |
| Tuesday – August 18 |
|
| Wednesday – August 19 |
|
| Thursday – August 20 |
|
Related Articles
Permanent Shutdown of Non-Company-Specific URLs 29Number of Views Identity Router (IDR) Software Version 12.22.0.0.37: Tomcat Upgrade and Removal of Non-Company-Specific URLs 171Number of Views Transitioning to Company-Specific URLs in RSA Authentication Manager (AM) 51Number of Views Sporadic 'Node verification failed' error messages in AM activity monitor 37Number of Views Company-Specific Administrative URLs Update Instructions 431Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide