5 Troubleshooting the RSA Authentication Manager Connector

This chapter provides solutions to problems you might encounter after you deploy or while using the RSA Authentication Manager connector.

Table 5-1 provides solutions to problems you might encounter with the RSA Authentication Manager connector.

Table 5-1 Troubleshooting for the RSA Authentication Manager Connector

Problem	Solution
The following error message is encountered: com.rsa.common.SystemException: Failed to construct CommandTarget	Ensure that you are using the right port in the IT resource parameter. Generally, the port used to access the RSA UI and the port used in the IT resource are different.
The following error message is encountered: com.rsa.command.exception.InvalidArgumentException: Static password does not meet policy requirements	Ensure that you are entering the passcode as per the policy defined in RSA Authentication Manager. Generally, the passcode should be between 4 to 8 characters, and should not contain any special characters.
The following error message is encountered: com.rsa.command.exception.InvalidArgumentException: Password policy not satisfied	Ensure that you enter the accurate password as per the policies specified in RSA Authentication Manager. The following are the predefined policies to set a password in the connector: Require at least alphabetic characters Require at least uppercase characters Require at least lowercase characters Require at least numeric characters Require at least special characters
The following error message is encountered: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://rsa.idc.oracle.com:7002: Destination unreachable; nested exception is: javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination]	This exception is encountered because the RSA certificate is incorrectly imported, or imported to the incorrect keystore. It is observed that this problem occurs if you have imported the certificate into the wrong keystore. You can fix this issue by checking the Oracle Identity Manager server logs for the correct keystore, and reimporting the same into it.
The following error message is encountered: com.rsa.command.AuditedLocalizableSystemException: COMMAND_EXECUTION_UNEXPECTED_ERROR	This exception is encountered because the <attributename> in the exception is not supported for filtering, but is being used as a filter. For supported attributes for filters, see .Limited Reconciliation