Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
SvetlanaKlasnic
New Contributor
New Contributor

Credit Agricole Serbia - RSA server

Jump to solution

Dear,

I am new RSA administrator in our bank. I followed the maintenance of the RSA server from my colleague who left this position. Old RSA Authentication Manager 7.1 server still working on Windows 2003 server with a lot of problems. Therefore, we are urgent to install a new RSA server. How  I do not who to ask, I am referring to you for advice how to get a new version of RSA Authentication Manager and witch Windows server and resources I need. I have got the contract with Asseco SE, Belgrade which states that we have purchased the manufacturer's support for AUT0000100BE1-8 SID Access Base EnhMnt 1Mo (80) 36 month 62.50 $x80=5,000.00 $.

I ask you to help as soon as possible.

Best regards,

          Svetlana Klašnić

          

-----------------------------------------------------------------------------------------------------------------------------------------------------

SENIOR SYSTEM ENGINEER FOR ADMINISTRATION

OF COMPUTER AND TELECOMMUNICATIONS NETWORKS

Information-Communication Tehnologies Sector

 

0 Likes
1 Solution

Accepted Solutions
EdwardDavis
Employee
Employee

The version you would be able to migrate to, is RSA Authentication Manager 8.1.x (highest version of 8.1 is 8.1 sp1 patch 15 or 8.1.1.15.0) Then later, 8.1.x can be upgraded to 8.2, then 8.3. But only 8.1.x can do a 7.x migration. They are all Suse Linux OS, and can be a virtual machine in Vmware, Hyper-v, or an RSA hardware appliance. If you have a valid maintenance contract you can request to download the base version of 8.1 to set up, so you have a machine to migrate to...and also you need to request a license upgrade from 7.1 to 8.1 for migration, so you can set up 8.1.

 

 

see this

000013065 - How to request a license for RSA Authentication Manager 8.x 

 

you need to 'migrate' the 7.1 license, that way the new one you get will be marked 8.1 and will be able

to install an 8.1 version (or 8.2 or 8.3). A license marked 8.2 or 8.3 cannot set up a new 8.1.

 

see this

000034558 - How to download RSA Authentication Manager 8.x full kits and service packs from RSA Link 

 

to migrate from 7...you need the 'Archive' downloads tab to find the original 8.1 images, not 8.2 or 8.3.

 

 

Basic overview:

set up 8.1.

Patch it to 8.1 sp1.

Patch it to 8.1 sp1 patch 15.

 

https://community.rsa.com/docs/DOC-36947 

 

In the patch 15 zip file are new migration tools you will run on the 7.1 primary to create a migration package that can be imported to 8.1 sp1 patch 15 operations console.

 

You are not forced to migrate to 8.1 sp1 patch 15, you can migrate to 8.1 base, but I recommend patching up as we have fixed a few things migration-related and if the target version is 8.1 sp1 patch 15 there is the best chance of not hitting any known issues.

View solution in original post

2 Replies
_EricaChalfin
Employee (Retired) Employee (Retired)
Employee (Retired)

Svetlana Klasnic‌,

 

I've moved your question to the RSA SecurID Access" data-type="space where it will be seen by the product's support engineers, other customers and partners.  Please bookmark this page and use it when you have product-specific questions.

 

Alternatively, from the RSA Customer Support" data-type="space page, click on Ask A Question on the blue navigation bar and choose Ask A Product Related Question.  From there, scroll to RSA SecurID Access" data-type="space and click Ask A Question.  That way your question will appear in the correct space.

Regards,

Erica

0 Likes
EdwardDavis
Employee
Employee

The version you would be able to migrate to, is RSA Authentication Manager 8.1.x (highest version of 8.1 is 8.1 sp1 patch 15 or 8.1.1.15.0) Then later, 8.1.x can be upgraded to 8.2, then 8.3. But only 8.1.x can do a 7.x migration. They are all Suse Linux OS, and can be a virtual machine in Vmware, Hyper-v, or an RSA hardware appliance. If you have a valid maintenance contract you can request to download the base version of 8.1 to set up, so you have a machine to migrate to...and also you need to request a license upgrade from 7.1 to 8.1 for migration, so you can set up 8.1.

 

 

see this

000013065 - How to request a license for RSA Authentication Manager 8.x 

 

you need to 'migrate' the 7.1 license, that way the new one you get will be marked 8.1 and will be able

to install an 8.1 version (or 8.2 or 8.3). A license marked 8.2 or 8.3 cannot set up a new 8.1.

 

see this

000034558 - How to download RSA Authentication Manager 8.x full kits and service packs from RSA Link 

 

to migrate from 7...you need the 'Archive' downloads tab to find the original 8.1 images, not 8.2 or 8.3.

 

 

Basic overview:

set up 8.1.

Patch it to 8.1 sp1.

Patch it to 8.1 sp1 patch 15.

 

https://community.rsa.com/docs/DOC-36947 

 

In the patch 15 zip file are new migration tools you will run on the 7.1 primary to create a migration package that can be imported to 8.1 sp1 patch 15 operations console.

 

You are not forced to migrate to 8.1 sp1 patch 15, you can migrate to 8.1 base, but I recommend patching up as we have fixed a few things migration-related and if the target version is 8.1 sp1 patch 15 there is the best chance of not hitting any known issues.