RADIUS cannot be managed after rebooting RSA AM server running 7.1 SP4 full kit.
Originally Published: 2012-03-15
Article Number
Applies To
RHEL Linux 5.8 64 bit
Cannot manage radius after rebooting the machine though all RSA services started.
Issue
RSAAuthenticationManager/imsoc/ops-console.log shows below error:
@@@2012-03-14 12:42:05,544 ERROR [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] GUILog.traceException(586) | exception:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://sacotpip02.sandisk.com:7082: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090504]Certificate chain received from sacotpip02.sandisk.com - 10.181.10.131 failed hostname verification check. Certificate contained sacotpip02.sdcorp.global.sandisk.com but check expected sacotpip02.sandisk.com; No available router to destination]
Cannot manage radius after rebooting the machine though all RSA services started.
Radius is configured with correct host name but after the configuration it shows a host name with incorrect domain suffix.
Related Articles
How to enable full debug WinSSHD Number of Views Full Refresh Deactivates Manual User Account Mappings in RSA Identity Governance & Lifecycle Number of Views Full interworking of a Cisco PIX firewall with KCA Number of Views RSA Governance & Lifecycle - Full Backup Script for Hardware Appliances or Software-Bundles with RSA-provided Database Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA-2026-07: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
