Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forÂ
Search instead forÂ
Did you mean:Â
Announcements
SecurID®
This is the primary landing page for SecurID, where customers and partners can find product documentation, downloads, advisories, forums and other helpful resources for the product.
hello team, i have migrated token to new RSA. sometimes not always i get "Authentication method failed, passcode format error". any specific reason for this error? Thanks in advance
... View more
Long story short I had to move my RSA server suddenly to a new FQDN and was unable to do the preparation via the console prior. Now when I go to the Operations Console I get "invalid request". I do have the machine running on the new IP addresses and I am able to SSH into the machine without issue. Version: 8.3 I'm in a bit of a jam in that I saw a few articles about changing an alias, but this is not even working with the FQDN to get to the operations console. I've seen numerous guides but they all assume you have access to the console which I do not.
... View more
Article Number
000068086
Applies To
SecurID Authentication Manager 8.1 up to 8.5
Issue
Radius failed on AM 8.4 after trying to add alternate IP to radius agent, Both primary and secondary radius tabs on the console are not opening and showing the error Image description " server unknown service is running You need to accurately configure a RADIUS server before you can view or edit any RADIUS Clients or Profiles." Image description " Connection to RADIUS server failed due to incorrect certificate."
Cause
Unknown
Resolution
Reconfiguration of RADIUS 1- Login to the Authentication Manager desired instance server via SSH, vSphere or direct connection. 2- Navigate to /opt/rsa/am/server 3- Stop the RADIUS service with the command ./rsaserv stop radius. 4- Navigate to /opt/rsa/am/config 5- Run the command ./config.sh RadiusOCConfig.configure. 6- Navigate to /opt/rsa/am/server 7- Start the RADIUS service with the command ./rsaserv start radius. After this RADIUS status should be back online and radius authentications will be back online
... View more
We are setting us a new server with IIS and RSA Securid to replace an existing server. One the new server we can successfully authenticate using RSA Securid soft token but when it gets redirected back to the website we get a 403 forbidden error. The 2 servers look to be set up s similar as possible. The old one has an old version of the agent (7.1) whilst the new one is using 8.0.5 Managed to get tracing to run but nothing obvious from that or the event logs. Any ideas or things to try?
... View more
Article Number
000068085
Applies To
Identity Router v2.17 update. ( Jan Release)
Issue
The IDR web resource are not accessible and are failing with following error in /var/log/symplified/*-error.log file. [ssl:info] AH02008: SSL library error 1 in handshake
[ssl:info] SSL Library Error: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher – Too restrictive SSLCipherSuite or using DSA server certificate?
[ssl:info] AH01998: Connection closed to child 20 with abortive shutdown
Cause
In IDR v2.17: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d) [openssl name - AES256-SHA256] and TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) [openssl name- AES256-SHA] are broken and fix is being pushed as part of Cloud Feb release.
If client apps in customer environment (browser/REST clients) are having only these two common ciphers in their cipher suites, the IDR web resource will be inaccessible due to no shared cipher.
Resolution
These 2 ciphers will be fixed as part of Cloud Feb release 2023
Workaround
Include more common cipher in the client side cipher suites. To find the other ciphers IDR support, please check https://community.rsa.com/t5/securid-cloud-authentication/security-levels-and-identity-router-connection-ciphers/ta-p/622927
... View more