Explanation | The Authentication Service is not configured with the JAAS Service. |
Action | No action is required. |
Explanation | The specified user ID, or the associated password, is not valid. |
Action | Verify that the user ID and password are entered correctly. Consult with the administrator of the user registry if the problem persist. |
Explanation | The specified client certificate does not map to a user in the registry. |
Action | Ensure the client supplies a certificate that maps to a user in the registry. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The authentication did not succeed because there is no JAR file for the JAAS custom login module. |
Action | Ensure the JAAS custom login module has a valid JAR file. |
Explanation | The authentication did not succeed because there is no login module defined for the login module reference. |
Action | Ensure the loginModuleRef element has a configured loginModule property. |
Explanation | An internal error occurred. |
Action | Contact IBM support. |
Explanation | The authentication did not succeed because the specified user ID is not valid. |
Action | Verify that the user ID is entered correctly. Consult with the administrator of the user registry if the problem persist. |
Explanation | The authentication did not succeed because the WSLoginModuleProxy options is null or empty. |
Action | Verify that the WSLoginModuleProxy configuration includes options. |
Explanation | The authentication did not succeed because the WSLoginModuleProxy delegate option is not set. |
Action | Verify that the WSLoginModuleProxy configuration includes the delegate option. |
Explanation | The WSLoginModuleProxy is not supported in the jaasLoginContextEntry system.DEFAULT. |
Action | Remove the proxy entry in logModuleRef of the jaasLoginContextEntry system.DEFAULT. |
Explanation | The jassLoginContextEntry has no login modules specified in the loginModuleRef. |
Action | Make sure that there is at least one login module specified in the loginModuleRef. |
Explanation | The userIDMap LDAP filter could not determine the display name of the user. The security name will be returned for the principal name for the programmatic API calls like getUserPrincipal. |
Action | If the user should have a displayName, make sure that the user is created in LDAP to match the userIdMap filter that is configured. |