The following table describes the error codes generated by the Authentication service. These errors are displayed to the user/administrator in the Authentication module.
Table D–2 Authentication Error Codes
Error Message |
Description/Probable Cause |
Action |
---|---|---|
authentication.already.login. |
The user has already logged in and has a valid session, but there is no Success URL redirect defined. |
Either logout, or set up some login success redirect URL(s) through the Access Manager Console. Use the ”goto’ query parameter with the value as Admin Console URL. |
logout.failure. |
A user is unable to logout of Access Manager. |
Restart the server. |
uncaught_exception |
An authentication Exception is thrown due to an incorrect handler |
Check the Login URL for any invalid or special characters. |
redirect.error |
Access Manager cannot redirect to Success or Failure redirect URL. |
Check the web container’s error log to see if there are any errors. |
gotoLoginAfterFail |
This link is generated when most errors occur. The link will send the user to the original Login URL page. | |
invalid.password |
The password entered is invalid. |
Passwords must contain at least 8 characters. Check that the password contains the appropriate amount of characters and ensure that it has not expired. |
auth.failed |
Authentication failed. This is the generic error message displayed in the default login failed template. The most common cause is invalid/incorrect credentials. |
Enter valid and correct user name/password (the credentials required by the invoked authentication module.) |
nouser.profile |
No user profile was found matching the the entered user name in the given organization. This error is displayed while logging in to the Membership/Self-registration authentication module. |
Enter your login information again. If this is your first login attempt, select New User in the login screen. |
notenough.characters |
The password entered does not contain enough characters. This error is displayed while logging in to the Membership/Self-registration authentication module. |
The login password must contain at least 8 characters by default (this number is configurable through the Membership Authentication module). |
useralready.exists |
A user already exists with this name in the given organization. This error is displayed while logging in to the Membership/Self-registration authentication module. |
User IDs must be unique within the organization. |
uidpasswd.same |
The User Name and Password fields cannot have the same value. This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure that the username and password are different. |
nouser.name |
No user name was entered.This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure to enter the user name. |
no.password |
No password was entered.This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure to enter the password. |
missing.confirm.passwd |
Missing the confirmation password field. This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure to enter the password in the Confirm Password field. |
password.mismatch |
The password and the confirm password do not match. This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure that the password and confirmation password match. |
An error occurred while storing the user profile. |
An error occurred while storing the user profile.This error is displayed while logging in to the Membership/Self-registration authentication module. |
Make sure that the attributes and elements are valid and correct for Self Registration in the Membership.xml file. |
orginactive |
This organization is not active. |
Activate the organization through the Access Manager console by changing the organization status from inactive to active. |
internal.auth.error |
Internal Authentication Error. This is a generic Authentication error which may be caused by different and multiple environmental and/or configuration issues. | |
usernot.active |
The user no longer has an active status. |
Activate the user through the Admin Console by changing the user status from inactive to active. if the user is locked out by Memory Locking, restart the server. |
user.not.inrole |
User does not belong to the specified role. This error is displayed during role-based authentication. |
Make sure that the login user belongs to the role specified for the role-based authentication. |
session.timeout |
The user session has timed out. |
Login in again. |
authmodule.denied |
The specified authentication module is denied. |
Make sure that the required authentication module is registered under the required organization, that the template is created and saved for the module, and that the module is selected in the Organization Authentication Modules list in the Core Authentication module. |
noconfig.found |
No configuration found. |
Check the Authentication Configuration service for the required authentication method. |
cookie.notpersistent |
Persistent Cookie Username does not exist in the Persistent Cookie Domain. | |
nosuch.domain |
The organization found. |
Make sure that the requested organization is valid and correct. |
userhasnoprofile.org |
User has no profile in the specified organization. |
Make sure that the user exists and is valid in the specified organization in the local Directory Server. |
reqfield.missing |
One of the required fields was not completed. Please make sure all required fields are entered. |
Make sure that all required fields are entered. |
session.max.limit |
Maximum Sessions Limit Reached. |
Logout and login again. |