000030321 - Authentication Manager 8.1 trusted realms not working (java.net.UnknownHostException)

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000030321
Applies ToRSA Product Set: SecurID
RSA Product/Service Type:  Authentication Manager 
RSA Version/Condition: 8.1
 
IssueTrusted realm authentication is not working properly.
Enabled the verbose for trace log on local Authentication Manager instance and see the following error message in imsTrace.log.
 
2015-05-25 15:04:00,453, [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:316), trace.com.rsa.command.EJBRemoteTargetBase, ERROR, am81pri.dc.rsa.shanghai.com,,,,Unable to connect to downgraded EJB/2.1 command server.null
2015-05-25 15:04:00,453, [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'], (EJBRemoteTarget.java:317), trace.com.rsa.command.EJBRemoteTargetBase, DEBUG, am81pri.dc.rsa.shanghai.com,,,,Unable to connect to downgraded EJB/2.1 command server.
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: marge.csau.ap.rsa.net]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:767)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)

 
CauseThe hostname of remote AM server can't be resolved or the remote AM server is offline.
ResolutionGo to Security Console - Administration - Trusted Realms - Manage Existing and do the following.
1. If the remote trusted realm no longer exists, delete the trusted realm.
2. If the hostname/ip of remote trusted realm has been changed, update the trusted realm package.
3. If the remote trusted realm server is offline, bring that server online and this issue should be automatically fixed.

Attachments

    Outcomes