RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Customers and support engineers need to know the exact Authentication Manager version installed in order to:
- Tell whether a known issue or security vulnerability affects their deployment, since many fixes apply only to specific service pack, patch or hotfix levels.
- Pick the correct upgrade path and update files, and confirm that a patch or hotfix will install on their current version.
- Make sure the primary instance, the replica instances and the Web Tier are all at matching versions.
- Give RSA Technical Support the full version string when opening a case, which speeds up troubleshooting.
Version strings such as 8.7 SP2 Patch 4 Hotfix 1 can be confusing. It isn't always clear which part refers to a release, a service pack, a patch or a hotfix, or how they relate to each other. Reading a version incorrectly can lead to installing the wrong update, failed upgrades, or missing a fix that is already available.
Using 8.7 SP2 Patch 4 Hotfix 1 as an example:
| Component | Example | Description |
| Major version | 8 | The Authentication Manager 8.x platform. |
| Minor release | 7 | A feature release with new functionality and component updates, installed as an upgrade. |
| Service pack | SP 2 | A cumulative update to the minor release. It includes all earlier patches and may add small features or platform changes. |
| Patch | 4 | A cumulative set of bug and security fixes for a specific service pack. Patch 4 includes the fixes in Patches 1 through 3. |
| Hotfix | 1 | A targeted fix for one or more specific issues, built for one exact patch level. |
Key rules
- Patches are cumulative within a service pack. You can install the latest patch for your service pack without installing the earlier ones first.
- Hotfixes are specific to one patch level. A hotfix built for 8.7 SP2 Patch 4 can only be installed on 8.7 SP2 Patch 4. Hotfix fixes are normally included in the next patch, so upgrading to the next patch replaces the hotfix.
- Install updates in order: service pack, then patch, then hotfix.
- Always update the primary instance first, then each replica instance.
- The Web Tier and authentication agents have their own version numbers. After you update Authentication Manager, check whether the Web Tier also needs an update.
To check the installed version
- Log on to the Operations Console.
- Click Maintenance > Update & Rollback. The installed version and update history are shown.
- You can also check from the Security Console under Help > About RSA Authentication Manager.
Notes Before you install any update, read its readme and release notes for prerequisites, the supported upgrade path, and any known issues.
You can see the versioning information in /opt/rsa/am/server/logs when various updates have been completed:
Related Articles
How to change username format in Authentication Manager 20Number of Views If the eserver drops a connection to the selfservice console the selfservice console does not attempt to reestablish a ne… 18Number of Views RSA Authentication Manager 8.7 SP2 Patch 1 Web Tier Readme 89Number of Views "Tokencode is incorrect" while attempting to resynchronize an RSA SecurID software token on RSA Authentication Manager 8.x 185Number of Views Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 655Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device