Additional error messages for this failure are as follows:
2013-06-28 11:21:39,749 DEBUG [pool-7-thread-1] com.rsa.authagent.authapi.logger.b - b.b():? - receive timeout: java.net.SocketTimeoutException: Receive t imed out 2013-06-28 11:21:39,750 DEBUG [pool-7-thread-1] com.rsa.authagent.authapi.logger.b - a.b():? - Error receiving request: com.rsa.ace.techservice.udpserver. a: Error receiving packet Timeout: java.net.SocketTimeoutException: Receive timed out 2013-06-28 11:21:39,750 DEBUG [pool-7-thread-1] com.rsa.authagent.authapi.logger.b - a.a():? - Response status is: 1 2013-06-28 11:21:39,750 DEBUG [pool-7-thread-1] com.rsa.authagent.authapi.logger.b - a.a():? - Authenticaton failed for TIME ! 2013-06-28 11:21:39,750 WARN [pool-7-thread-1] com.rsa.authagent.authapi.logger.c - User TIME's access is denied.
The Access Manager server which uses the Authentication Manager api jar was on a multihomed host and the Authentication API client is unable to bind to Authentication Manager.
You must set the correct IP address from which the authentication will be sent (the IP address of the Access Manager authentication server) in either the aserver.conf or the auth api jar file's rsa_api.properties file.IP.
In the aserver.conf:
In rsa_api.properties file:
#RSA Authentication API Properties #Override Host IP Address RSA_AGENT_HOST=xxx.xxx.xxx.xxx
In the context mentioned in this solution, the User TIME is not a real user or the user that tried to authenticate. It is indicating a timeout on the test server message.