Category: Server Extensions

Severity: ERROR

Message: An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s.

Severity: ERROR

Message: An error occurred while attempting to base64-decode the password value %s: %s.

Severity: ERROR

Message: The %s password storage scheme is not reversible, so it is impossible to recover the plaintext version of an encoded password.

Severity: ERROR

Message: An error occurred while trying to register the JMX alert handler with the MBean server: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to encode a password using the storage scheme defined in class %s: %s.

Severity: ERROR

Message: The ds-cfg-include-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are included in the cache, has an invalid value of "%s": %s.

Severity: ERROR

Message: The ds-cfg-exclude-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are excluded from the cache, has an invalid value of "%s": %s.

Severity: ERROR

Message: A fatal error occurred while trying to initialize fifo entry cache: %s.

Severity: ERROR

Message: A fatal error occurred while trying to initialize soft reference entry cache: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode the password modify extended request sequence: %s.

Severity: ERROR

Message: The password modify extended request cannot be processed because it does not contain an authorization ID and the underlying connection is not authenticated.

Severity: ERROR

Message: The password modify extended request cannot be processed because the server was unable to obtain a write lock on user entry %s after multiple attempts.

Severity: ERROR

Message: The password modify extended request cannot be processed because the server cannot decode "%s" as a valid DN for use in the authorization ID for the operation.

Severity: ERROR

Message: The password modify extended request cannot be processed because it contained an invalid userIdentity field. The provided userIdentity string was "%s".

Severity: ERROR

Message: The password modify extended request cannot be processed because it was not possible to identify the user entry to update based on the authorization DN of "%s".

Severity: ERROR

Message: The password modify extended operation cannot be processed because the current password provided for the user is invalid.

Severity: ERROR

Message: The keystore file %s specified in attribute ds-cfg-key-store-file of configuration entry %s does not exist.

Severity: ERROR

Message: An error occurred while trying to load the keystore contents from file %s: %s.

Severity: ERROR

Message: The keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s.

Severity: ERROR

Message: An error occurred while trying to access the PKCS#11 key manager: %s.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of keystore file %s: %s.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of the PKCS#11 keystore: %s.

Severity: ERROR

Message: The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist.

Severity: ERROR

Message: An error occurred while trying to load the trust store contents from file %s: %s.

Severity: ERROR

Message: An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s.

Severity: ERROR

Message: The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate subject "%s" could not be decoded as an LDAP DN: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because an error occurred while attempting to retrieve the user entry with DN "%s": %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because no user entry exists with a DN of %s.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the associated bind request does not have a reference to the client connection.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the associated client connection instance is not an instance of LDAPClientConnection.

Severity: ERROR

Message: The SASL EXTERNAL bind request could not be processed because the client did not present a certificate chain during SSL/TLS negotiation.

Severity: ERROR

Message: The SASL EXTERNAL bind request failed because the certificate chain presented by the client during SSL/TLS negotiation could not be mapped to a user entry in the Directory Server.

Severity: ERROR

Message: StartTLS cannot be used on this connection because the underlying client connection is not available.

Severity: ERROR

Message: StartTLS cannot be used on this client connection because this connection type is not capable of using StartTLS to protect its communication.

Severity: ERROR

Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s does not have any certificates with which to verify the presented peer certificate.

Severity: ERROR

Message: Unable to authenticate via SASL EXTERNAL because the mapped user entry %s did not contain the peer certificate presented by the client.

Severity: ERROR

Message: An error occurred while attempting to validate the peer certificate presented by the client with a certificate from the user's entry %s: %s.

Severity: ERROR

Message: SASL PLAIN authentication requires that SASL credentials be provided but none were included in the bind request.

Severity: ERROR

Message: The SASL PLAIN bind request did not include any NULL characters. NULL characters are required as delimiters between the authorization ID and authentication ID, and also between the authentication ID and the password.

Severity: ERROR

Message: The SASL PLAIN bind request did not include a second NULL character in the credentials, which is required as a delimiter between the authentication ID and the password.

Severity: ERROR

Message: The authentication ID contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the authentication ID.

Severity: ERROR

Message: The password contained in the SASL PLAIN bind request had a length of zero characters, which is not allowed. SASL PLAIN authentication does not allow an empty string for use as the password.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL PLAIN authentication ID "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The authentication ID in the SASL PLAIN bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based authentication ID of a SASL PLAIN bind request: %s.

Severity: ERROR

Message: The server was not able to find any user entries for the provided authentication ID of %s.

Severity: ERROR

Message: The provided password is invalid.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request contained SASL credentials but there is no stored challenge for this client connection. The first CRAM-MD5 bind request in the two-stage process must not contain client SASL credentials.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request contained SASL credentials, but the stored SASL state information for this client connection is not in an appropriate form for the challenge.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request from the client included SASL credentials but there was no space to separate the username from the authentication digest.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest string had an invalid length of %d bytes rather than the %d bytes expected for a hex representation of an MD5 digest.

Severity: ERROR

Message: The SASL CRAM-MD5 bind request included SASL credentials, but the decoded digest was not comprised of only hexadecimal digits: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL CRAM-MD5 username "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The username in the SASL CRAM-MD5 bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL CRAM-MD5 bind request: %s.

Severity: ERROR

Message: The server was not able to find any user entries for the provided username of %s.

Severity: ERROR

Message: The provided password is invalid.

Severity: ERROR

Message: SASL CRAM-MD5 authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

Severity: ERROR

Message: The client connection included %s state information, indicating that the client was in the process of performing a %s bind, but the bind request did not include any credentials.

Severity: ERROR

Message: An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s.

Severity: ERROR

Message: An unexpected error occurred while trying to create an %s context: %s.

Severity: ERROR

Message: An error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %s.

Severity: ERROR

Message: The username in the SASL %s bind request appears to be an empty DN. This is not allowed.

Severity: ERROR

Message: An error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %s.

Severity: ERROR

Message: The username contained in the SASL %s bind request had a length of zero characters, which is not allowed. %s authentication does not allow an empty string for use as the username.

Severity: ERROR

Message: The server was not able to find any user entries for the provided username of %s.

Severity: ERROR

Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR

Message: The entry %s specified as the authorization identity does not exist.

Severity: ERROR

Message: The entry %s specified as the authorization identity could not be retrieved: %s.

Severity: ERROR

Message: The server was unable to find any entry corresponding to authorization ID %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %s.

Severity: ERROR

Message: SASL %s authentication is not possible for user %s because none of the passwords in the user entry are stored in a reversible form.

Severity: ERROR

Message: SASL %s protocol error: %s.

Severity: ERROR

Message: The authenticating user %s does not have sufficient privileges to assume a different authorization identity.

Severity: ERROR

Message: The authenticating user %s does not have sufficient access to assume a different authorization identity.

Severity: ERROR

Message: The server was unable to find any entry corresponding to authentication ID %s.

Severity: ERROR

Message: The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s.

Severity: ERROR

Message: An error occurred while attempting to create the JAAS login context for GSSAPI authentication: %s.

Severity: ERROR

Message: No client connection was available for use in processing the GSSAPI bind request.

Severity: ERROR

Message: You do not have sufficient privileges to use the proxied authorization control.

Severity: ERROR

Message: ID string %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to resolve ID string %s to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: An error occurred while attempting to map username %s to a Directory Server entry: %s.

Severity: ERROR

Message: Unable to process the cancel request because the extended operation did not include a request value.

Severity: ERROR

Message: An error occurred while attempting to decode the value of the cancel extended request: %s.

Severity: ERROR

Message: Password storage scheme %s does not support use with the authentication password attribute syntax.

Severity: ERROR

Message: The configured minimum password length of %d characters is greater than the configured maximum password length of %d.

Severity: ERROR

Message: The provided password is shorter than the minimum required length of %d characters.

Severity: ERROR

Message: The provided password is longer than the maximum allowed length of %d characters.

Severity: ERROR

Message: Configuration entry "%s" does not contain attribute ds-cfg-password-character-set which specifies the sets of characters that should be used when generating the password. This is a required attribute.

Severity: ERROR

Message: Configuration entry "%s" contains multiple definitions for the %s character set.

Severity: ERROR

Message: An error occurred while attempting to decode the value(s) of the configuration attribute ds-cfg-password-character-set, which is used to hold the character set(s) for use in generating the password: %s.

Severity: ERROR

Message: The password format string "%s" references an undefined character set "%s".

Severity: ERROR

Message: The password format string "%s" contains an invalid syntax. This value should be a comma-delimited sequence of elements, where each element is the name of a character set followed by a colon and the number of characters to choose at random from that character set.

Severity: ERROR

Message: An error occurred while attempting to decode the value for configuration attribute ds-cfg-password-format, which is used to specify the format for the generated passwords: %s.

Severity: ERROR

Message: An error occurred while attempting to get the password policy for user %s: %s.

Severity: ERROR

Message: The current password must be provided for self password changes.

Severity: ERROR

Message: Password modify operations that supply the user's current password must be performed over a secure communication channel.

Severity: ERROR

Message: End users are not allowed to change their passwords.

Severity: ERROR

Message: Password changes must be performed over a secure communication channel.

Severity: ERROR

Message: The password cannot be changed because the previous password change was too recent.

Severity: ERROR

Message: The password cannot be changed because it is expired.

Severity: ERROR

Message: No new password was provided, and no password generator has been defined that may be used to automatically create a new password.

Severity: ERROR

Message: An error occurred while attempting to create a new password using the password generator: %s.

Severity: ERROR

Message: The password policy does not allow users to supply pre-encoded passwords.

Severity: ERROR

Message: The provided new password failed the validation checks defined in the server: %s.

Severity: ERROR

Message: Unable to encode the provided password using the default scheme(s): %s.

Severity: ERROR

Message: An error occurred while attempting to determine the identity mapper to use in conjunction with the password modify extended operation defined in configuration entry %s: %s. The password modify extended operation will not be enabled for use in the server.

Severity: ERROR

Message: The provided authorization ID string "%s" could not be mapped to any user in the directory.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID string "%s" to a user entry: %s.

Severity: ERROR

Message: An error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL CRAM-MD5 authentication: %s.

Severity: ERROR

Message: An error occurred while attempting to verify the password for user %s during SASL PLAIN authentication: %s.

Severity: ERROR

Message: The user account has been administratively disabled.

Severity: ERROR

Message: The user account is locked.

Severity: ERROR

Message: Unable to examine entry %s as a potential member of static group %s because that entry does not exist in the Directory Server.

Severity: ERROR

Message: An error occurred while attempting to retrieve entry %s as a potential member of static group %s: %s.

Severity: ERROR

Message: Entry %s cannot be parsed as a valid static group because static groups are not allowed to have both the %s and %s object classes.

Severity: ERROR

Message: Entry %s cannot be parsed as a valid static group because it does not contain exactly one of the %s or the %s object classes.

Severity: ERROR

Message: Value %s for attribute %s in entry %s cannot be parsed as a valid DN: %s. It will be excluded from the set of group members.

Severity: ERROR

Message: You do not have sufficient privileges to perform password reset operations.

Severity: ERROR

Message: The provided authorization ID was empty, which is not allowed for DIGEST-MD5 authentication.

Severity: ERROR

Message: The provided authorization ID %s contained an invalid DN: %s.

Severity: ERROR

Message: The authenticating user %s does not have sufficient privileges to specify an alternate authorization ID.

Severity: ERROR

Message: The entry corresponding to authorization DN %s does not exist in the Directory Server.

Severity: ERROR

Message: An error occurred while attempting to retrieve entry %s specified as the authorization ID: %s.

Severity: ERROR

Message: No entry corresponding to authorization ID %s was found in the server.

Severity: ERROR

Message: An error occurred while attempting to map authorization ID %s to a user entry: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Configuration entry %s has value '%s' which violates the format required for attribute mappings. The expected format is 'certattr:userattr'.

Severity: ERROR

Message: Configuration entry %s contains multiple mappings for certificate attribute %s.

Severity: ERROR

Message: Mapping %s in configuration entry %s references attribute %s which is not defined in the server schema.

Severity: ERROR

Message: Configuration entry %s contains multiple mappings for user attribute %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: Unable to decode peer certificate subject %s as a DN: %s.

Severity: ERROR

Message: Peer certificate subject %s does not contain any attributes for which a mapping has been established.

Severity: ERROR

Message: The certificate with subject %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user entry because no peer certificate was available.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the peer certificate was not an X.509 certificate (peer certificate format was %s).

Severity: ERROR

Message: An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s.

Severity: ERROR

Message: The certificate with fingerprint %s could not be mapped to exactly one user. It maps to both %s and %s.

Severity: ERROR

Message: Unable to decode value "%s" in entry "%s" as an LDAP URL: %s.

Severity: ERROR

Message: Dynamic groups do not support explicitly altering their membership.

Severity: ERROR

Message: An error occurred while attempting perform an internal search with base DN %s and filter %s to resolve the member list for dynamic group %s: result code %s, error message %s.

Severity: ERROR

Message: The server encountered a timeout while attempting to add user %s to the member list for dynamic group %s.

Severity: ERROR

Message: The provided password differs less than the minimum required difference of %d characters.

Severity: ERROR

Message: The provided password contained too many instances of the same character appearing consecutively. The maximum number of times the same character may appear consecutively in a password is %d.

Severity: ERROR

Message: The provided password does not contain enough unique characters. The minimum number of unique characters that may appear in a user password is %d.

Severity: ERROR

Message: The %s attribute is not searchable and should not be included in otherwise unindexed search filters.

Severity: ERROR

Message: The provided password contained a word from the server's dictionary.

Severity: ERROR

Message: The specified dictionary file %s does not exist.

Severity: ERROR

Message: An error occurred while attempting to load the dictionary from file %s: %s.

Severity: ERROR

Message: The provided password was found in another attribute in the user entry.

Severity: ERROR

Message: The provided password contained character '%s' which is not allowed for use in passwords.

Severity: ERROR

Message: The provided password did not contain enough characters from the character set '%s'. The minimum number of characters from that set that must be present in user passwords is %d.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character set.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because the provided character set is empty.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

Severity: ERROR

Message: The provided character set definition '%s' is invalid because it contains character '%s' which has already been used.

Severity: ERROR

Message: The virtual static group defined in entry %s contains multiple target group DNs, but only one is allowed.

Severity: ERROR

Message: Unable to decode "%s" as the target DN for group %s: %s.

Severity: ERROR

Message: The virtual static group defined in entry %s does not contain a target group definition.

Severity: ERROR

Message: Target group %s referenced by virtual static group %s does not exist.

Severity: ERROR

Message: Altering membership for virtual static group %s is not allowed.

Severity: ERROR

Message: Virtual static group %s references target group %s which is itself a virtual static group. One virtual static group is not allowed to reference another as its target group.

Severity: ERROR

Message: You do not have sufficient privileges to use the password policy state extended operation.

Severity: ERROR

Message: The provided password policy state extended request did not include a request value.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode password policy state extended request value: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s.

Severity: ERROR

Message: No value was provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the disabled state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: The value provided for the password policy state operation intended to set the disabled state for the user was invalid. The value must be either 'true' or 'false'.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the account expiration time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the account expiration time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the password changed time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the password changed time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the password warned time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the password warned time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to add an authentication failure time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to update the authentication failure times was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the last login time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the last login time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: No value was provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the reset state for the user. Exactly one value (either 'true' or 'false') must be given.

Severity: ERROR

Message: The value provided for the password policy state operation intended to set the reset state for the user was invalid. The value must be either 'true' or 'false'.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to add a grace login use time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to update the grace login use times was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: Multiple values were provided for the password policy state operation intended to set the required change time for the user. Exactly one value must be given.

Severity: ERROR

Message: The value %s provided for the password policy state operation used to set the required change time was invalid: %s. The value should be specified using the generalized time format.

Severity: ERROR

Message: The password policy state extended request included an operation with an invalid or unsupported operation type of %s.

Severity: ERROR

Message: The provided new password was already contained in the password history.

Severity: ERROR

Message: The Directory Server is not configured with any SMTP servers. The SMTP alert handler cannot be used unless the Directory Server is configured with information about at least one SMTP server.

Severity: ERROR

Message: The provided match pattern "%s" could not be parsed as a regular expression: %s.

Severity: ERROR

Message: The processed ID string %s is mapped to multiple users.

Severity: ERROR

Message: The internal search based on processed ID string %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to resolve processed ID string %s to a user entry: %s.

Severity: ERROR

Message: Group instance with DN %s has been deleted and is no longer valid.

Severity: ERROR

Message: The SMTP account status notification handler defined in configuration entry %s cannot be enabled unless the Directory Server is with information about one or more SMTP servers.

Severity: ERROR

Message: SMTP account status notification handler configuration entry '%s' does not include any email address attribute types or recipient addresses. At least one of these must be provided.

Severity: ERROR

Message: Unable to parse message subject value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the subject.

Severity: ERROR

Message: Unable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

Severity: ERROR

Message: The message subject definitions contained in configuration entry '%s' have multiple subjects defined for notification type %s.

Severity: ERROR

Message: Unable to parse message template file path value '%s' from configuration entry '%s' because the value does not contain a colon to separate the notification type from the template file path.

Severity: ERROR

Message: Unable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification type.

Severity: ERROR

Message: The message template file path definitions contained in configuration entry '%s' have multiple template file paths defined for notification type %s.

Severity: ERROR

Message: The message template file '%s' referenced in configuration entry '%s' does not exist.

Severity: ERROR

Message: An unclosed token was found starting at column %d of line %d.

Severity: ERROR

Message: The notification-user-attr token starting at column %d of line %d references undefined attribute type %s.

Severity: ERROR

Message: The notification-property token starting at column %d of line %d references undefined notification property %s.

Severity: ERROR

Message: An unrecognized token %s was found at column %d of line %d.

Severity: ERROR

Message: An error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %s.

Severity: ERROR

Message: An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %s.

Severity: ERROR

Message: An error occurred while trying to encrypt a value using password storage scheme %s: %s.

Severity: ERROR

Message: An error occurred while trying to decrypt a value using password storage scheme %s: %s.

Severity: ERROR

Message: Cannot decode the provided symmetric key extended operation because it does not have a value.

Severity: ERROR

Message: Cannot decode the provided symmetric key extended request: %s.

Severity: ERROR

Message: An unexpected error occurred while attempting to decode the symmetric key extended request sequence: %s.

Severity: ERROR

Message: Failed to create a SASL server for SASL mechanism %s.

Severity: ERROR

Message: GSSAPI SASL mechanism handler initalization failed because the keytab file %s does not exist.

Severity: ERROR

Message: The password value %s has been base64-decoded but is too short to be valid.

Severity: ERROR

Message: The provided minimum required number of character sets '%d' is invalid because it must at least include all mandatory character sets.

Severity: ERROR

Message: The provided minimum required number of character sets '%d' is invalid because it is greater than the total number of defined character sets.

Severity: ERROR

Message: The provided password did not contain characters from at least %d of the following character sets or ranges: %s.

Severity: ERROR

Message: An error occurred while attempting to decode member's DN %s of static group %s: %s.

Severity: ERROR

Message: SASL %s authentication is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: Password modification is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: The password policy state extended operation is not supported for user %s because the account is not managed locally.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the following mapping attributes were not found in the user's entry: %s.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search of base DN "%s" returned more than one entry matching the filter "%s".

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s".

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %s.

Severity: ERROR

Message: The user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %s.

Severity: ERROR

Message: The configuration of LDAP PTA policy "%s" is invalid because it does not specify the a means for obtaining the mapped search bind password.

Severity: ERROR

Message: The certificate with subject %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

Severity: ERROR

Message: The certificate with subject %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with subject %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with subject %s to a user entry: %s.

Severity: ERROR

Message: The certificate with fingerprint %s mapped to multiple users.

Severity: ERROR

Message: The internal search based on the certificate with fingerprint %s could not be processed efficiently: %s. Check the server configuration to ensure that all associated backends are properly configured for these types of searches.

Severity: ERROR

Message: An internal failure occurred while attempting to map the certificate with fingerprint %s to a user entry: %s.

Severity: ERROR

Message: The provided password did not contain enough characters from the character range '%s'. The minimum number of characters from that range that must be present in user passwords is %d.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because it does not contain a colon to separate the minimum count from the character range.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the value before the colon must be an integer greater or equal to zero.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is reversed.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is missing the minus.

Severity: ERROR

Message: The provided character range definition '%s' is invalid because the range '%s' is too short.

Severity: ERROR

Message: There is no private key entry in keystore '%s' used by file based key manager provider '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private key.

Severity: ERROR

Message: An error occurred while attempting to match a bcrypt hashed password value: %s.

Severity: ERROR

Message: The mapped search filter template "%s" could not be parsed as a valid LDAP filter.

Severity: ERROR

Message: An error occurred while trying to create a key manager factory to access the contents of LDAP keystore with base DN '%s': %s.

Severity: ERROR

Message: An error occurred while trying to create a trust manager factory to access the certificates in "cn=admin data": %s.

Severity: ERROR

Message: An error occurred while trying to create a trust manager factory to access the contents of the PKCS#11 keystore: %s.

Severity: ERROR

Message: An error occurred while trying to access the PKCS#11 trust manager: %s.

Severity: ERROR

Message: Unable to load JVM default keystore from system properties: %s.

Severity: ERROR

Message: An error occurred while reading information contained within key manager provider from configuration: "%s".

Severity: ERROR

Message: Unable to get the JVM default truststore: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user becausethe peer certificate issuer "%s" could not be decoded as an LDAP DN: %s.

Severity: ERROR

Message: Could not map the provided certificate chain to a user because the matching user entry with DN '%s' does not contain an issuer DN matching the certificate issuer DN '%s'.

Severity: ERROR

Message: The baseDN '%s' specified as match base DN in the exact match identity mapper defined in configuration entry '%s', does not belong to a local backend.

Severity: ERROR

Message: The baseDN '%s' specified as match base DN in the regular expression identity mapper defined in configuration entry '%s', does not belong to a local backend.

Severity: ERROR

Message: The processed ID string %s is mapped to multiple users.

Severity: ERROR

Message: File based key manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR

Message: File based key manager provider '%s' cannot load an X509 extended key manager from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR

Message: File based key manager provider '%s' cannot load content from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %s.

Severity: ERROR

Message: File based trust manager provider '%s' cannot load content from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %s.

Severity: ERROR

Message: File based trust manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this trust manager provider may fail. Ensure that truststore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR

Message: File based trust manager provider '%s' cannot load an X509 extended trust manager from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'.

Severity: ERROR

Message: The %s SCRAM password storage scheme could not be initialized because the algorithm is not supported by the JVM.

Severity: ERROR

Message: An error occurred while attempting to decode the SCRAM credential value %s: %s.

Severity: ERROR

Message: SASL %s authentication is not possible for user '%s' because the user entry does not contain any SCRAM credentials.

Severity: ERROR

Message: An error occurred while attempting to retrieve the SCRAM credentials for user '%s' in order to perform SASL %s authentication: %s.

Severity: ERROR

Message: The %s SCRAM SASL mechanism handler could not be initialized because the algorithm is not supported by the JVM.

Severity: ERROR

Message: Error loading dictionary: %s.