SSL Socket Connection Error with RSA Authentication Agent versions 7.3.1 [48] through 7.3.2 [80] and Authentication Manager 8.4 +
Originally Published: 2019-11-25
Last Modified: 2023-09-24
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4.
RSA Authentication Agent: versions 7.3.1 [48] through 7.3.2 [80]
Issue
"RSA Authentication Agent versions 7.3.1 [48] through 7.3.2 [80] were linked with a BSAFE version where the TLS 1.2 handshake was broken but still worked by negotiating down to TLS 1.1"
Authentication Manager 8.4 and higher uses only TLS 1.2.
SSL Socket Connection Errors can be seen in the System Activity Monitor or by running a System Log Report via the Security Console.
| 2019-11-25 14:58:56 | WARN | 26246 | SSL Socket Connection Error | SSL handshake exception occurred with the remote host “Agent IP Address” communicating over the SSL channel:“No shared ciphers for protocol” | Warning | Remote client communicates over unsupported SSL/TLS channel. | SYSTEM |
Resolution
| Upgrade your Windows agents to the latest version; that is, an agent later than 7.3.2 [85] for this particular problem. |
Notes
| https://community.rsa.com/docs/DOC-95921 |
Related Articles
SSL socket connection error with RSA Authentication Agent for Windows 7.3.1 [48] through 7.3.2 [80] and Authentication Man… 133Number of Views User groups 12Number of Views Cloud Administration Delete User Device API 9Number of Views RSA Authentication Manager 6.1 to 8.0 Migration Guide 37Number of Views How to edit the Account custom attribute which is marked as managed in RSA Identity Governance and Lifecycle 60Number of Views
Trending Articles
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 RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?