RSA SecurID Access

Hello Paul,   Yes there is a way, Please follow the below steps: 1. SSH on the primary server  2. /opt/rsa/am/utils/rsautil manage-secrets -a get com.rsa.db.dba.password 3. /opt/rsa/am/pgsql/bin/psql -h localhost -p 7050 -d db -U rsa_dba 4. enter the password fetched in step 2 5. in my case the read only user is <rouser>, all you nee to do…

1.Does this mean, we can upgrade 1 Primary and 5 replicas in "one change window"  WITHOUT any downtime of users?? Yes, all the authentications will be redirected randomly to the other 5 replicas    2.Do we upgrade first primary and then just replica instances to 8.5?? or do we need any switchover of instances before upgrades on replicas You…

Hello,   Please check the article below on how to download the electronic tokens RSA Announces Electronic RSA SecurID Software Token Enablement    Thanks Gee

Hello Kiran,   Primary and replica are working in an Active Active protocol,   If the primary is Down, the replica will takes place for Authentications only, since the replica is a Read-Only server, you cannot do any administrative activities on it, and regarding the automatic Switch when the primary is Down, this is not applicable Promotion has…

Hello,   The Replica must be in the same subnet as the primary, but it must have different FQDN and different IP from the Primary of course  If you found out that there is a problem in the replication which you can on Operations Console > home Page > replication status  You are most welcome to open a Support case as this require an…

Hello,   1. Make sure that the NTP server is reachable from the replica side,  2. Make sure that you have 2 NTP servers configured in the Operations Console of replica > Administration > Date & Time. 3. SSH on the server, and run    ntpq -n  check the results and the offset   Thanks, Gee

Hello,   Passcode format error, is a general error, that defines that the passcode you entered is incorrect,   So, please 1. Test first authentication on the SSC ( https://<Primaryhostname>/ssc), to make sure that you are doing the authentication in a correct way, 2. If the auth succeeded on SSC, try again on the Radius Client. 3. if not, you…

Hello,   Please check the guide below: Manage Relying Parties    Thanks,  Gee

Hello James,   If we are dealing with Radius Authentications, you needed to make sure that the Ip of the replica is configured on the third party side, else it will not redirect the authentications,   Can you clarify more what was the agent type and if you are sure that the replicas are configured on the third party clients    Thanks, Gee

There are two reasons a user entering a passcode can get prompted for a Next Token Code, NTC  1. They have failed a number of passcode authentications with that token - Security Console - Auth - Policy - Tokens  2. The TokenCode that was entered (Passcode=TokenCode+PIN) is slightly outside of the Window of acceptable tokencodes for that…