Explanation | The entity type must be defined with an entity type name and at least one corresponding Relative Distinguished Name (RDN) property. |
Action | Modify and correct the entity type definition in the server.xml file. |
Explanation | The specified base entry definition is invalid. |
Action | Specify a valid base entry definition in the server.xml file. |
Explanation | The specified base entry definition is invalid. |
Action | Specify a valid base entry definition in the server.xml file. |
Explanation | The realm tag is missing, or is invalid because of a missing required attribute. |
Action | Modify and correct the realm definition in the server.xml file. |
Explanation | The specified definition of the participating base entry is incorrect. The syntax for defining a participating base entry is <participatingBaseEntry name="..."/>. |
Action | Modify and correct the participating base entry definition in the server.xml file. |
Explanation | The mapping definition of the user registry attribute is defined incorrectly. |
Action | Modify and correct the mapping definition of the user registry attribute in the server.xml file. |
Explanation | The specified realm name is not defined or is incorrect in the server.xml file. |
Action | Ensure that the realm name exists and it is spelt correctly in the server.xml file. If it does not exist, a valid realm must be specified. |
Explanation | At least one valid participating base entry must be defined for a realm. |
Action | Ensure that a valid participating base entry is defined for the realm in the server.xml file. |
Explanation | After adding a repository, at least one base entry must be added to it. |
Action | Add at least one base entry to the repository in the server.xml file. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A user registry was not defined or could not be initialized due to a configuration error. A valid user registry includes an LDAP registry or other supported registries or repositories. |
Action | If a user registry was defined in the configuration file, review the logs for configuration errors during server start up. Add or correct the user registry definition in the server.xml file. |
Explanation | When the failed login delay is disabled, the server is vulnerable to a user enumeration style attack. |
Action | Enable the failed login delay by removing the attributes to use the default minimum and maximum padding delay of zero and 5000 milliseconds or set the attributes to a custom configuration. |