RSA Authentication Manager 8.2 SP1 to 8.4. What steps required to upgrade and file download location. Thanks.
RSA Authentication Manager 8.4 has not yet been released. Our most recent version is Authentication Manager 8.3, available from RSA Authentication Manager 8.3 Downloads. After installing or upgrading to 8.3, you can then apply RSA Authentication Manager 8.3 Patch 2 - Update Download and RSA Authentication Manager 8.3 Patch 2 - Web-Tier Server Download.
What i the version you have installed now so I can provide you with the upgrade path?
When AM 8.4 comes out, you could do this they way we have been doing this since AM 8.1 SP1.
1. Update primary one patch, update replicas to the same patch one at a time
a. Apply the AM 8.3 update to your AM 8.2 SP1 P6 Primary
b. Apply the AM 8.3 update to your AM 8.2 SP1 P6 Replica, or if replicas, one at a time
c. Apply the AM 8.4 update to your AM 8.3 Primary
d. Apply the AM 8.4 update to your AM 8.3 Replica, or if replicas, one at a time
e. update any web tiers
This approach keeps your realm as is, just updating the versions. Refer to 000029877 - How to install patches on an RSA Authentication Manager 8.1 via web browser
2. Back in AM 8.0 and AM 8.1, there was a feature holdover from AM 7.1, where you could restore a backup from a previous version into a newer current version, e.g. restore an AM 8.0 P4 backup into an AM 8.1 P3 server. Since AM 8.2 every backup restore must be to the same version that the backup was taken in. With this feature, you could
a. deploy a new AM Primary
b. restore a backup from your previous version Primary in the operations console of the current primary.
c. deploy and attach new Replicas
d. deploy new web tiers as needed
This feature, if it came back, would not make sense with hardware appliances.
Hi Jay Guillette
I have small / silly question after restore any allowed older version to 8.4, what is the version of AM after successful restore ? if we take backup from new instance(8.4) can that be restore to another 8.4 instance(new)?
Rajesh [M.Tech Products Pte Ltd]
When this feature is supported in AM 8.4, if you restore a backup from AM 8.2 SP1 or AM 8.3, after the backup restore the Primary will still be AM 8.4, but basically the system will look like the AM 8.2 SP1 or AM 8.3 system, same agents, tokens, users and same Identity Sources, but with the name and IP of the AM 8.4 system.
I screamed in my head (REALLY!?) was looking to make sure P2 was the latest and almost freaking had a heart attack at seeing something about 8.4. I am taking my sour gummies and going home.
8.3 P3 came out today.
I blame Frank Miller.
An excellent rule: when in doubt, blame Frank Miller
Thanks- Do you have to clear node secrets and re upload SD CONF files on your authentication agents ?
If you are upgrading your Authentication Manager instances to 8.4, you should not have to reestablish node secrets with your agents or reapply the sdconf.rec.
Please let me know if your question has been answered.
Jay Guillette. What is the expected release date for Authentication Manager 8.4? Will there be an updated authentication agent as well?
AM 8.4 is scheduled for end of this year, but the restore from earlier version backup feature has been pushed out to a later version or patch.
updating agents is not dependent on updating servers, unless you are looking for some new features. If you are happy with your agents, leave them at their current version and then look at reasons to update your agent versions independently after the AM servers are updated.
Examples are UDP port 5500 agents, even some pretty old versions, still work fine against AM 8.3 and will work with AM 8.4, but if you need something like the ReST authentication API to authenticate against TCP port 5555, either from some Policy reason (no UDP!) or for the ability to authenticate against the Access Cloud service a SecurID Access Identity Router, IDR, then you will want the Next Gen agents version 8.x, either for PAM - already released, or for Windows when it comes out.
Retrieving data ...