| | |
| | | be preloaded into the entry cache |
| | | SEVERE_ERR_CACHE_PRELOAD_ENTRY_FAILED_15=Failed to preload %s entry into \ |
| | | the entry cache: %s |
| | | MILD_ERR_EXTOP_PASSMOD_ILLEGAL_REQUEST_ELEMENT_TYPE_32=The password modify \ |
| | | extended request sequence included an ASN.1 element of an invalid type: %s |
| | | MILD_ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUEST_33=An unexpected error occurred \ |
| | | while attempting to decode the password modify extended request sequence: %s |
| | | MILD_ERR_EXTOP_PASSMOD_NO_AUTH_OR_USERID_34=The password modify extended \ |
| | |
| | | MILD_ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZID_38=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" |
| | | MILD_ERR_EXTOP_PASSMOD_NO_DN_BY_AUTHZID_39=The password modify extended \ |
| | | request cannot be processed because the provided authorization UID of "%s" \ |
| | | did not match any entries in the directory |
| | | MILD_ERR_EXTOP_PASSMOD_MULTIPLE_ENTRIES_BY_AUTHZID_40=The password modify \ |
| | | extended request cannot be processed because the provided authorization UID \ |
| | | of "%s" matched more than one entry in the directory |
| | | MILD_ERR_EXTOP_PASSMOD_INVALID_OLD_PASSWORD_41=The password modify extended \ |
| | | operation cannot be processed because the current password provided for the \ |
| | | user is invalid |
| | |
| | | containing the Directory Server keystore information. Changes to this \ |
| | | configuration attribute will take effect the next time that the key manager \ |
| | | is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_NO_FILE_ATTR_44=The configuration entry %s that \ |
| | | defines a file-based key manager does not contain attribute \ |
| | | ds-cfg-key-store-file that should hold the path to the keystore file |
| | | SEVERE_ERR_FILE_KEYMANAGER_NO_SUCH_FILE_45=The keystore file %s specified in \ |
| | | attribute ds-cfg-key-store-file of configuration entry %s does not exist |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_FILE_46=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-file in configuration entry %s: %s |
| | | INFO_FILE_KEYMANAGER_DESCRIPTION_TYPE_47=Keystore type for the \ |
| | | Directory Server keystore. Valid values should always include 'JKS' and \ |
| | | 'PKCS12', but different implementations may allow other values as well. If \ |
| | | no value is provided, then the JVM-default value will be used. Changes to \ |
| | | this configuration attribute will take effect the next time that the key \ |
| | | manager is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_TYPE_48=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-type in configuration entry %s: %s |
| | | INFO_FILE_KEYMANAGER_DESCRIPTION_PIN_PROPERTY_49=Name of the \ |
| | | Java property that contains the clear-text PIN needed to access the \ |
| | | file-based key manager. Changes to this configuration attribute will take \ |
| | | effect the next time that the key manager is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_PIN_PROPERTY_NOT_SET_50=Java property %s which is \ |
| | | specified in attribute ds-cfg-key-store-pin-property of configuration entry \ |
| | | %s should contain the PIN needed to access the file-based key manager, but \ |
| | | this property is not set |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_PIN_PROPERTY_51=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-property in configuration entry %s: %s |
| | | INFO_FILE_KEYMANAGER_DESCRIPTION_PIN_ENVAR_52=Name of the \ |
| | | environment variable that contains the clear-text PIN needed to access the \ |
| | | file-based key manager. Changes to this configuration attribute will take \ |
| | | effect the next time that the key manager is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_PIN_ENVAR_NOT_SET_53=Environment variable %s which \ |
| | | is specified in attribute ds-cfg-key-store-pin-environment-variable of \ |
| | | configuration entry %s should contain the PIN needed to access the file-based \ |
| | | key manager, but this property is not set |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_PIN_ENVAR_54=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-environment-variable in configuration entry %s: %s |
| | | INFO_FILE_KEYMANAGER_DESCRIPTION_PIN_FILE_55=Path to the text \ |
| | | file whose only contents should be a single line containing the clear-text \ |
| | | PIN needed to access the file-based key manager. Changes to this \ |
| | | configuration attribute will take effect the next time that the key manager \ |
| | | is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_PIN_NO_SUCH_FILE_56=File %s specified in attribute \ |
| | | ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN \ |
| | | needed to access the file-based key manager, but this file does not exist |
| | |
| | | SEVERE_ERR_FILE_KEYMANAGER_PIN_FILE_EMPTY_58=File %s specified in attribute \ |
| | | ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN \ |
| | | needed to access the file-based key manager, but this file is empty |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_PIN_FILE_59=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-file in configuration entry %s: %s |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_DETERMINE_PIN_FROM_ATTR_60=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin in configuration entry %s: %s |
| | |
| | | load the keystore contents from file %s: %s |
| | | SEVERE_ERR_FILE_KEYMANAGER_INVALID_TYPE_63=The keystore type %s specified in \ |
| | | attribute ds-cfg-key-store-type of configuration entry %s is not valid: %s |
| | | INFO_FILE_KEYMANAGER_UPDATED_FILE_64=The value of the ds-cfg-key-store-file \ |
| | | attribute in configuration entry %s has been updated to %s. The new value \ |
| | | will take effect the next time the key manager is accessed |
| | | INFO_FILE_KEYMANAGER_UPDATED_TYPE_65=The value of the ds-cfg-key-store-type \ |
| | | attribute in configuration entry %s has been updated to %s. The new value \ |
| | | will take effect the next time the key manager is accessed |
| | | INFO_FILE_KEYMANAGER_UPDATED_PIN_66=The PIN to use to access the file-based \ |
| | | key manager has been updated. The new value will take effect the next time \ |
| | | the key manager is accessed |
| | | INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_PROPERTY_67=Name of the \ |
| | | Java property that contains the clear-text PIN needed to access the PKCS#11 \ |
| | | key manager. Changes to this configuration attribute will take effect the \ |
| | | next time that the key manager is accessed |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_PIN_PROPERTY_NOT_SET_68=Java property %s which \ |
| | | is specified in attribute ds-cfg-key-store-pin-property of configuration \ |
| | | entry %s should contain the PIN needed to access the PKCS#11 key manager, but \ |
| | | this property is not set |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_DETERMINE_PIN_PROPERTY_69=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-property in configuration entry %s: %s |
| | | INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_ENVAR_70=Name of the \ |
| | | environment variable that contains the clear-text PIN needed to access the \ |
| | | PKCS#11 key manager. Changes to this configuration attribute will take \ |
| | | effect the next time that the key manager is accessed |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_PIN_ENVAR_NOT_SET_71=Environment variable %s \ |
| | | which is specified in attribute ds-cfg-key-store-pin-environment-variable of \ |
| | | configuration entry %s should contain the PIN needed to access the PKCS#11 \ |
| | | key manager, but this property is not set |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_DETERMINE_PIN_ENVAR_72=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-environment-variable in configuration entry %s: %s |
| | | INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_FILE_73=Path to the text \ |
| | | file whose only contents should be a single line containing the clear-text \ |
| | | PIN needed to access the PKCS#11 key manager. Changes to this configuration \ |
| | | attribute will take effect the next time that the key manager is accessed |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_PIN_NO_SUCH_FILE_74=File %s specified in \ |
| | | attribute ds-cfg-key-store-pin-file of configuration entry %s should contain \ |
| | | the PIN needed to access the PKCS#11 key manager, but this file does not \ |
| | |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_PIN_FILE_EMPTY_76=File %s specified in attribute \ |
| | | ds-cfg-key-store-pin-file of configuration entry %s should contain the PIN \ |
| | | needed to access the PKCS#11 key manager, but this file is empty |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_DETERMINE_PIN_FILE_77=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin-file in configuration entry %s: %s |
| | | INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_ATTR_78=Clear-text PIN \ |
| | | needed to access the PKCS#11 key manager. Changes to this configuration \ |
| | | attribute will take effect the next time that the key manager is accessed |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_DETERMINE_PIN_FROM_ATTR_79=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-key-store-pin in configuration entry %s: %s |
| | |
| | | attribute ds-cfg-key-store-pin |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_LOAD_81=An error occurred while trying to \ |
| | | access the PKCS#11 key manager: %s |
| | | INFO_PKCS11_KEYMANAGER_UPDATED_PIN_82=The PIN to use to access the PKCS#11 \ |
| | | key manager has been updated. The new value will take effect the next time \ |
| | | the key manager is accessed |
| | | SEVERE_ERR_FILE_KEYMANAGER_CANNOT_CREATE_FACTORY_83=An error occurred while \ |
| | | trying to create a key manager factory to access the contents of keystore \ |
| | | file %s: %s |
| | | SEVERE_ERR_PKCS11_KEYMANAGER_CANNOT_CREATE_FACTORY_84=An error occurred while \ |
| | | trying to create a key manager factory to access the contents of the PKCS#11 \ |
| | | keystore: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_FILE_85=Path to the file \ |
| | | containing the Directory Server trust store information. Changes to this \ |
| | | configuration attribute will take effect the next time that the trust manager \ |
| | | is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_NO_FILE_ATTR_86=The configuration entry %s that \ |
| | | defines a file-based trust manager does not contain attribute \ |
| | | ds-cfg-trust-store-file that should hold the path to the trust store file |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_NO_SUCH_FILE_87=The trust store file %s \ |
| | | specified in attribute ds-cfg-trust-store-file of configuration entry %s does \ |
| | | not exist |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_FILE_88=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-file in configuration entry %s: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_TYPE_89=Keystore type for \ |
| | | the Directory Server trust store. Valid values should always include 'JKS' \ |
| | | and 'PKCS12', but different implementations may allow other values as well. \ |
| | | If no value is provided, then the JVM-default value will be used. Changes to \ |
| | | this configuration attribute will take effect the next time that the trust \ |
| | | manager is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_TYPE_90=An unexpected error \ |
| | | occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-type in configuration entry %s: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_PIN_PROPERTY_91=Name of the \ |
| | | Java property that contains the clear-text PIN needed to access the \ |
| | | file-based trust manager. Changes to this configuration attribute will take \ |
| | | effect the next time that the trust manager is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_PIN_PROPERTY_NOT_SET_92=Java property %s which \ |
| | | is specified in attribute ds-cfg-trust-store-pin-property of configuration \ |
| | | entry %s should contain the PIN needed to access the file-based trust \ |
| | | manager, but this property is not set |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_PIN_PROPERTY_93=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-pin-property in configuration entry %s: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_PIN_ENVAR_94=Name of the \ |
| | | environment variable that contains the clear-text PIN needed to access the \ |
| | | file-based trust manager. Changes to this configuration attribute will take \ |
| | | effect the next time that the trust manager is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_PIN_ENVAR_NOT_SET_95=Environment variable %s \ |
| | | which is specified in attribute ds-cfg-trust-store-pin-environment-variable \ |
| | | of configuration entry %s should contain the PIN needed to access the \ |
| | | file-based trust manager, but this property is not set |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_PIN_ENVAR_96=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-pin-environment-variable in configuration entry %s: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_PIN_FILE_97=Path to the text \ |
| | | file whose only contents should be a single line containing the clear-text \ |
| | | PIN needed to access the file-based trust manager. Changes to this \ |
| | | configuration attribute will take effect the next time that the trust manager \ |
| | | is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_PIN_NO_SUCH_FILE_98=File %s specified in \ |
| | | attribute ds-cfg-trust-store-pin-file of configuration entry %s should \ |
| | | contain the PIN needed to access the file-based trust manager, but this file \ |
| | |
| | | attribute ds-cfg-trust-store-pin-file of configuration entry %s should \ |
| | | contain the PIN needed to access the file-based trust manager, but this file \ |
| | | is empty |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_PIN_FILE_101=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-pin-file in configuration entry %s: %s |
| | | INFO_FILE_TRUSTMANAGER_DESCRIPTION_PIN_ATTR_102=Clear-text PIN \ |
| | | needed to access the file-based trust manager. Changes to this configuration \ |
| | | attribute will take effect the next time that the trust manager is accessed |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_PIN_FROM_ATTR_103=An unexpected \ |
| | | error occurred while trying to determine the value of configuration attribute \ |
| | | ds-cfg-trust-store-pin in configuration entry %s: %s |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_LOAD_104=An error occurred while trying \ |
| | | to load the trust store contents from file %s: %s |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_CREATE_FACTORY_105=An error occurred \ |
| | |
| | | SEVERE_ERR_FILE_TRUSTMANAGER_INVALID_TYPE_106=The trust store type %s \ |
| | | specified in attribute ds-cfg-trust-store-type of configuration entry %s is \ |
| | | not valid: %s |
| | | INFO_FILE_TRUSTMANAGER_UPDATED_FILE_107=The value of the \ |
| | | ds-cfg-trust-store-file attribute in configuration entry %s has been updated \ |
| | | to %s. The new value will take effect the next time the trust manager is \ |
| | | accessed |
| | | INFO_FILE_TRUSTMANAGER_UPDATED_TYPE_108=The value of the \ |
| | | ds-cfg-trust-store-type attribute in configuration entry %s has been updated \ |
| | | to %s. The new value will take effect the next time the trust manager is \ |
| | | accessed |
| | | INFO_FILE_TRUSTMANAGER_UPDATED_PIN_109=The PIN to use to access the \ |
| | | file-based trust manager has been updated. The new value will take effect \ |
| | | the next time the trust manager is accessed |
| | | MILD_ERR_SEDCM_NO_PEER_CERTIFICATE_118=Could not map the provided certificate \ |
| | | chain to a user entry because no peer certificate was available |
| | | MILD_ERR_SEDCM_PEER_CERT_NOT_X509_119=Could not map the provided certificate \ |
| | |
| | | MILD_ERR_SASLEXTERNAL_NOT_LDAP_CLIENT_INSTANCE_124=The SASL EXTERNAL bind \ |
| | | request could not be processed because the associated client connection \ |
| | | instance is not an instance of LDAPClientConnection |
| | | MILD_ERR_SASLEXTERNAL_CLIENT_NOT_USING_TLS_PROVIDER_125=The SASL EXTERNAL \ |
| | | bind request could not be processed because the client connection is not \ |
| | | using the TLS security provider (client security provider is %s). The TLS \ |
| | | security provider is required for clients that wish to use SASL EXTERNAL \ |
| | | authentication |
| | | MILD_ERR_SASLEXTERNAL_NO_CLIENT_CERT_126=The SASL EXTERNAL bind request could \ |
| | | not be processed because the client did not present a certificate chain \ |
| | | during SSL/TLS negotiation |
| | |
| | | MILD_ERR_STARTTLS_NOT_TLS_CAPABLE_129=StartTLS cannot be used on this client \ |
| | | connection because this connection type is not capable of using StartTLS to \ |
| | | protect its communication |
| | | MILD_ERR_STARTTLS_ERROR_ON_ENABLE_130=An unexpected error occurred while \ |
| | | attempting to enable the TLS connection security manager on the client \ |
| | | connection for the purpose of StartTLS: %s |
| | | INFO_SASLEXTERNAL_DESCRIPTION_VALIDATION_POLICY_131=Indicates whether the \ |
| | | SASL EXTERNAL mechanism handler should attempt to validate the peer \ |
| | | certificate against a certificate in the corresponding user's entry. The \ |
| | | value must be one of "true" (which will always attempt to validate the \ |
| | | certificate and will fail if no certificates are present), "false" (which \ |
| | | will never attempt to validate the peer certificate), and "ifpresent" (which \ |
| | | will validate the peer certificate if there are one or more certificates in \ |
| | | the user's entry, but will not fail if there are no certificates in the \ |
| | | entry. Changes to this configuration attribute will take effect immediately |
| | | SEVERE_ERR_SASLEXTERNAL_INVALID_VALIDATION_VALUE_132=Configuration entry %s \ |
| | | has an invalid value %s for attribute \ |
| | | ds-cfg-certificate-validation-policy. The value must be one of \ |
| | | "always", "never", or "ifpresent" |
| | | SEVERE_ERR_SASLEXTERNAL_CANNOT_GET_VALIDATION_POLICY_133=An unexpected error \ |
| | | occurred while attempting to determine the value of the \ |
| | | ds-cfg-certificate-validation-policy attribute in configuration entry \ |
| | | %s: %s |
| | | INFO_SASLEXTERNAL_DESCRIPTION_CERTIFICATE_ATTRIBUTE_134=Name of \ |
| | | the attribute that will be used to hold the certificate information in user \ |
| | | entries for the purpose of validation. This must specify the name of a valid \ |
| | | attribute type defined in the server schema. Changes to this configuration \ |
| | | attribute will take effect immediately |
| | | SEVERE_ERR_SASLEXTERNAL_CANNOT_GET_CERT_ATTR_135=An unexpected error occurred \ |
| | | while attempting to determine the value of the ds-cfg-certificate-attribute \ |
| | | attribute in configuration entry %s: %s |
| | | SEVERE_ERR_SASLEXTERNAL_UNKNOWN_CERT_ATTR_136=The attribute %s referenced in \ |
| | | configuration attribute ds-cfg-certificate-attribute in configuration entry \ |
| | | %s does not exist in the Directory Server schema. The attribute that is to \ |
| | | be used for certificate validation during SASL EXTERNAL authentication must \ |
| | | be defined in the server schema |
| | | MILD_ERR_SASLEXTERNAL_NO_CERT_IN_ENTRY_137=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 |
| | |
| | | MILD_ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERT_139=An error occurred while \ |
| | | attempting to validate the peer certificate presented by the client with a \ |
| | | certificate from the user's entry %s: %s |
| | | INFO_SASLEXTERNAL_UPDATED_VALIDATION_POLICY_140=Attribute \ |
| | | ds-cfg-certificate-validation-policy in configuration entry %s has \ |
| | | been updated. The new client certificate validation policy is %s |
| | | INFO_SASLEXTERNAL_UPDATED_CERT_ATTR_141=Attribute \ |
| | | ds-cfg-certificate-attribute in configuration entry %s has been updated. The \ |
| | | %s attribute will now be used when validating peer certificates |
| | | INFO_SASLPLAIN_DESCRIPTION_USERNAME_ATTRIBUTE_142=Name of the \ |
| | | attribute that will be used to identify user entries based on the \ |
| | | authcID/authzID provided during SASL PLAIN authentication. This must specify \ |
| | | the name of a valid attribute type defined in the server schema. Changes to \ |
| | | this configuration attribute will take effect immediately |
| | | SEVERE_ERR_SASLPLAIN_CANNOT_GET_USERNAME_ATTR_143=An unexpected error \ |
| | | occurred while attempting to determine the value of the \ |
| | | ds-cfg-user-name-attribute attribute in configuration entry %s: %s |
| | | SEVERE_ERR_SASLPLAIN_UNKNOWN_USERNAME_ATTR_144=The attribute %s referenced in \ |
| | | configuration attribute ds-cfg-user-name-attribute in configuration entry %s \ |
| | | does not exist in the Directory Server schema. The attribute that is to be \ |
| | | used for username lookups during SASL PLAIN authentication must be defined in \ |
| | | the server schema |
| | | INFO_SASLPLAIN_DESCRIPTION_USER_BASE_DN_145=Base DN that should \ |
| | | be used when searching for entries based on the authcID/authzID provided \ |
| | | during SASL PLAIN authentication. Changes to this configuration attribute \ |
| | | will take effect immediately |
| | | SEVERE_ERR_SASLPLAIN_CANNOT_GET_USER_BASE_DN_146=An unexpected error occurred \ |
| | | while attempting to determine the value of the ds-cfg-user-base-dn attribute \ |
| | | in configuration entry %s: %s |
| | | MILD_ERR_SASLPLAIN_NO_SASL_CREDENTIALS_147=SASL PLAIN authentication requires \ |
| | | that SASL credentials be provided but none were included in the bind request |
| | | MILD_ERR_SASLPLAIN_NO_NULLS_IN_CREDENTIALS_148=The SASL PLAIN bind request \ |
| | |
| | | MILD_ERR_SASLPLAIN_CANNOT_GET_ENTRY_BY_DN_154=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 |
| | | MILD_ERR_SASLPLAIN_CANNOT_PERFORM_INTERNAL_SEARCH_155=An error occurred while \ |
| | | trying to perform an internal search to retrieve the user entry associated \ |
| | | with the SASL PLAIN authentication ID %s. The result of that search was %s \ |
| | | with a message of %s |
| | | MILD_ERR_SASLPLAIN_MULTIPLE_MATCHING_ENTRIES_156=The internal search \ |
| | | attempting to resolve SASL PLAIN authentication ID %s matched multiple \ |
| | | entries. Authentication cannot succeed unless the authentication ID is \ |
| | | mapped to exactly one user entry |
| | | MILD_ERR_SASLPLAIN_NO_MATCHING_ENTRIES_157=The server was not able to find \ |
| | | any user entries for the provided authentication ID of %s |
| | | MILD_ERR_SASLPLAIN_NO_PW_ATTR_158=The SASL PLAIN authentication failed \ |
| | | because the mapped user entry did not contain any values for the %s attribute |
| | | MILD_ERR_SASLPLAIN_UNKNOWN_STORAGE_SCHEME_159=A password in the target user \ |
| | | entry %s could not be processed via SASL PLAIN because that password has an \ |
| | | unknown storage scheme of %s |
| | | MILD_ERR_SASLPLAIN_INVALID_PASSWORD_160=The provided password is invalid |
| | | INFO_SASLPLAIN_UPDATED_USERNAME_ATTR_161=Attribute ds-cfg-user-name-attribute \ |
| | | in configuration entry %s has been updated. The %s attribute will now be \ |
| | | used when looking up user entries based on their authcID/authzID |
| | | INFO_SASLPLAIN_UPDATED_USER_BASE_DN_162=Attribute ds-cfg-user-base-dn in \ |
| | | configuration entry %s has been updated. The DN %s will now be used as the \ |
| | | search base when looking up user entries based on their authcID/authzID |
| | | INFO_SASLPLAIN_CANNOT_LOCK_ENTRY_163=The Directory Server was unable to \ |
| | | obtain a read lock on user entry %s in order to retrieve that entry |
| | | MILD_ERR_SEDCM_CANNOT_LOCK_ENTRY_164=The Directory Server was unable to \ |
| | |
| | | SEVERE_ERR_SASLCRAMMD5_CANNOT_GET_MESSAGE_DIGEST_166=An unexpected error \ |
| | | occurred while attempting to obtain an MD5 digest engine for use by the \ |
| | | CRAM-MD5 SASL handler: %s |
| | | INFO_SASLCRAMMD5_DESCRIPTION_USERNAME_ATTRIBUTE_167=Name of the \ |
| | | attribute that will be used to identify user entries based on the username \ |
| | | provided during SASL CRAM-MD5 authentication. This must specify the name of \ |
| | | a valid attribute type defined in the server schema. Changes to this \ |
| | | configuration attribute will take effect immediately |
| | | SEVERE_ERR_SASLCRAMMD5_CANNOT_GET_USERNAME_ATTR_168=An unexpected error \ |
| | | occurred while attempting to determine the value of the \ |
| | | ds-cfg-user-name-attribute attribute in configuration entry %s: %s |
| | | SEVERE_ERR_SASLCRAMMD5_UNKNOWN_USERNAME_ATTR_169=The attribute %s referenced \ |
| | | in configuration attribute ds-cfg-user-name-attribute in configuration entry \ |
| | | %s does not exist in the Directory Server schema. The attribute that is to \ |
| | | be used for username lookups during SASL CRAM-MD5 authentication must be \ |
| | | defined in the server schema |
| | | INFO_SASLCRAMMD5_DESCRIPTION_USER_BASE_DN_170=Base DN that \ |
| | | should be used when searching for entries based on the username provided \ |
| | | during SASL CRAM-MD5 authentication. Changes to this configuration attribute \ |
| | | will take effect immediately |
| | | SEVERE_ERR_SASLCRAMMD5_CANNOT_GET_USER_BASE_DN_171=An unexpected error \ |
| | | occurred while attempting to determine the value of the ds-cfg-user-base-dn \ |
| | | attribute in configuration entry %s: %s |
| | | MILD_ERR_SASLCRAMMD5_NO_STORED_CHALLENGE_172=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 \ |
| | |
| | | MILD_ERR_SASLCRAMMD5_CANNOT_GET_ENTRY_BY_DN_180=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 |
| | | MILD_ERR_SASLCRAMMD5_ZERO_LENGTH_USERNAME_181=The username contained in the \ |
| | | SASL CRAM-MD5 bind request had a length of zero characters, which is not \ |
| | | allowed. CRAM-MD5 authentication does not allow an empty string for use as \ |
| | | the username |
| | | MILD_ERR_SASLCRAMMD5_CANNOT_PERFORM_INTERNAL_SEARCH_182=An error occurred \ |
| | | while trying to perform an internal search to retrieve the user entry \ |
| | | associated with the SASL CRAM-MD5 username %s. The result of that search was \ |
| | | %s with a message of %s |
| | | MILD_ERR_SASLCRAMMD5_MULTIPLE_MATCHING_ENTRIES_183=The internal search \ |
| | | attempting to resolve SASL CRAM-MD5 username %s matched multiple entries. \ |
| | | Authentication cannot succeed unless the username is mapped to exactly one \ |
| | | user entry |
| | | MILD_ERR_SASLCRAMMD5_NO_MATCHING_ENTRIES_184=The server was not able to find \ |
| | | any user entries for the provided username of %s |
| | | MILD_ERR_SASLCRAMMD5_NO_PW_ATTR_185=The SASL CRAM-MD5 authentication failed \ |
| | | because the mapped user entry did not contain any values for the %s attribute |
| | | MILD_ERR_SASLCRAMMD5_UNKNOWN_STORAGE_SCHEME_186=A password in the target user \ |
| | | entry %s could not be processed via SASL CRAM-MD5 because that password has \ |
| | | an unknown storage scheme of %s |
| | | MILD_ERR_SASLCRAMMD5_CANNOT_GET_CLEAR_PASSWORD_187=An error occurred while \ |
| | | attempting to obtain the clear-text password for user %s from the value with \ |
| | | storage scheme %s: %s |
| | | MILD_ERR_SASLCRAMMD5_INVALID_PASSWORD_188=The provided password is invalid |
| | | MILD_ERR_SASLCRAMMD5_NO_REVERSIBLE_PASSWORDS_189=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 |
| | | INFO_SASLCRAMMD5_UPDATED_USERNAME_ATTR_190=Attribute \ |
| | | ds-cfg-user-name-attribute in configuration entry %s has been updated. The \ |
| | | %s attribute will now be used when looking up user entries based on their \ |
| | | username |
| | | INFO_SASLCRAMMD5_UPDATED_USER_BASE_DN_191=Attribute ds-cfg-user-base-dn in \ |
| | | configuration entry %s has been updated. The DN %s will now be used as the \ |
| | | search base when looking up user entries based on their username |
| | | INFO_SASL_UNSUPPORTED_CALLBACK_192=An unsupported or unexpected callback was \ |
| | | provided to the SASL server for use during %s authentication: %s |
| | | MILD_ERR_SASL_NO_CREDENTIALS_193=The client connection included \ |
| | |
| | | the authorization identity could not be retrieved: %s |
| | | MILD_ERR_SASL_AUTHZID_NO_MAPPED_ENTRY_205=The server was unable to \ |
| | | find any entry corresponding to authorization ID %s |
| | | MILD_ERR_SASL_CANNOT_MAP_AUTHZID_206=An error occurred while \ |
| | | attempting to map authorization ID %s to a user entry: %s |
| | | MILD_ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDS_207=An error occurred \ |
| | | while attempting to retrieve the clear-text password(s) for user %s in order \ |
| | | to perform SASL %s authentication: %s |
| | |
| | | fully qualified domain name of: %s |
| | | SEVERE_ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES_277=You do not have \ |
| | | sufficient privileges to use the proxied authorization control |
| | | INFO_EXACTMAP_DESCRIPTION_MATCH_ATTR_298=Name or OID of the \ |
| | | attribute whose value should exactly match the ID string provided to this \ |
| | | identity mapper. At least one value must be provided. All values must refer \ |
| | | to the name or OID of an attribute type defined in the Directory Server \ |
| | | schema. If multiple attribute type names or OIDs are provided, then at least \ |
| | | one of those attributes must contain the provided ID string value in exactly \ |
| | | one entry |
| | | MILD_ERR_EXACTMAP_NO_MATCH_ATTR_299=Configuration entry %s does not have any \ |
| | | values for attribute ds-cfg-match-attribute, which is used to specify which \ |
| | | attribute(s) may be used to map a given ID string to a user entry |
| | | MILD_ERR_EXACTMAP_UNKNOWN_ATTR_300=Configuration entry %s contains value %s \ |
| | | for attribute ds-cfg-match-attribute but that is not a valid name or OID for \ |
| | | any attribute type defined in the Directory Server schema |
| | | MILD_ERR_EXACTMAP_CANNOT_DETERMINE_MATCH_ATTR_301=An error occurred while \ |
| | | attempting to process the value(s) of attribute ds-cfg-match-attribute in \ |
| | | configuration entry %s: %s |
| | | INFO_EXACTMAP_DESCRIPTION_SEARCH_BASE_302=Base DN(s) that \ |
| | | should be used when performing searches to map the provided ID string to a \ |
| | | user entry. If no values are provided, then the root DSE will be used as the \ |
| | | search base |
| | | MILD_ERR_EXACTMAP_CANNOT_DETERMINE_MATCH_BASE_303=An error occurred while \ |
| | | attempting to process the value(s) of attribute ds-cfg-match-base-dn in \ |
| | | configuration entry %s: %s |
| | | INFO_EXACTMAP_UPDATED_MATCH_ATTRS_304=The set of attributes to use when \ |
| | | matching ID strings to user entries contained in attribute \ |
| | | ds-cfg-match-attribute of configuration entry %s has been updated |
| | | INFO_EXACTMAP_UPDATED_MATCH_BASES_305=The set of search base DNs to use when \ |
| | | matching ID strings to user entries contained in attribute \ |
| | | ds-cfg-match-base-dn of configuration entry %s has been updated |
| | | MILD_ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_306=ID string %s mapped to \ |
| | | multiple users |
| | | MILD_ERR_EXACTMAP_INEFFICIENT_SEARCH_307=The internal search based on ID \ |
| | |
| | | for these types of searches |
| | | MILD_ERR_EXACTMAP_SEARCH_FAILED_308=An internal failure occurred while \ |
| | | attempting to resolve ID string %s to a user entry: %s |
| | | INFO_SASLCRAMMD5_DESCRIPTION_IDENTITY_MAPPER_DN_309=DN of the \ |
| | | configuration entry that holds the configuration for the identity mapper that \ |
| | | should be used to map the CRAM-MD5 username to a Directory Server user entry. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | MILD_ERR_SASLCRAMMD5_NO_IDENTITY_MAPPER_ATTR_310=Configuration entry %s does \ |
| | | not contain attribute ds-cfg-identity-mapper which specifies the DN of the \ |
| | | identity mapper to use in conjunction with the CRAM-MD5 SASL mechanism. This \ |
| | | is a required attribute |
| | | MILD_ERR_SASLCRAMMD5_NO_SUCH_IDENTITY_MAPPER_311=The identity mapper %s \ |
| | | specified in attribute ds-cfg-identity-mapper of configuration entry %s \ |
| | | does not reference a valid identity mapper configuration that is enabled for \ |
| | | use in the Directory Server |
| | | MILD_ERR_SASLCRAMMD5_CANNOT_GET_IDENTITY_MAPPER_312=An error occurred while \ |
| | | trying to process the value of the ds-cfg-identity-mapper attribute in \ |
| | | configuration entry %s to determine which identity mapper should be used in \ |
| | | conjunction with the CRAM-MD5 SASL mechanism: %s |
| | | MILD_ERR_SASLCRAMMD5_CANNOT_MAP_USERNAME_313=An error occurred while \ |
| | | attempting to map username %s to a Directory Server entry: %s |
| | | INFO_SASLCRAMMD5_UPDATED_IDENTITY_MAPPER_314=Attribute \ |
| | | ds-cfg-identity-mapper in configuration entry %s has been updated. The \ |
| | | identity mapper defined in configuration entry %s will now be used to map \ |
| | | usernames to entries when processing SASL CRAM-MD5 bind requests |
| | | INFO_SASLDIGESTMD5_DESCRIPTION_IDENTITY_MAPPER_DN_315=DN of the \ |
| | | configuration entry that holds the configuration for the identity mapper that \ |
| | | should be used to map the DIGEST-MD5 username to a Directory Server user \ |
| | | entry. Changes to this configuration attribute will take effect immediately |
| | | MILD_ERR_SASLDIGESTMD5_NO_IDENTITY_MAPPER_ATTR_316=Configuration entry %s \ |
| | | does not contain attribute ds-cfg-identity-mapper which specifies the DN \ |
| | | of the identity mapper to use in conjunction with the DIGEST-MD5 SASL \ |
| | | mechanism. This is a required attribute |
| | | MILD_ERR_SASLDIGESTMD5_NO_SUCH_IDENTITY_MAPPER_317=The identity mapper %s \ |
| | | specified in attribute ds-cfg-identity-mapper of configuration entry %s \ |
| | | does not reference a valid identity mapper configuration that is enabled for \ |
| | | use in the Directory Server |
| | | MILD_ERR_SASLDIGESTMD5_CANNOT_GET_IDENTITY_MAPPER_318=An error occurred while \ |
| | | trying to process the value of the ds-cfg-identity-mapper attribute in \ |
| | | configuration entry %s to determine which identity mapper should be used in \ |
| | | conjunction with the DIGEST-MD5 SASL mechanism: %s |
| | | MILD_ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAME_319=An error occurred while \ |
| | | attempting to map username %s to a Directory Server entry: %s |
| | | INFO_SASLDIGESTMD5_UPDATED_IDENTITY_MAPPER_320=Attribute \ |
| | | ds-cfg-identity-mapper in configuration entry %s has been updated. The \ |
| | | identity mapper defined in configuration entry %s will now be used to map \ |
| | | usernames to entries when processing SASL DIGEST-MD5 bind requests |
| | | INFO_SASLPLAIN_DESCRIPTION_IDENTITY_MAPPER_DN_321=DN of the \ |
| | | configuration entry that holds the configuration for the identity mapper that \ |
| | | should be used to map the provided username to a Directory Server user entry. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | MILD_ERR_SASLPLAIN_NO_IDENTITY_MAPPER_ATTR_322=Configuration entry %s does \ |
| | | not contain attribute ds-cfg-identity-mapper which specifies the DN of the \ |
| | | identity mapper to use in conjunction with the PLAIN SASL mechanism. This is \ |
| | | a required attribute |
| | | MILD_ERR_SASLPLAIN_NO_SUCH_IDENTITY_MAPPER_323=The identity mapper %s \ |
| | | specified in attribute ds-cfg-identity-mapper of configuration entry %s \ |
| | | does not reference a valid identity mapper configuration that is enabled for \ |
| | | use in the Directory Server |
| | | MILD_ERR_SASLPLAIN_CANNOT_GET_IDENTITY_MAPPER_324=An error occurred while \ |
| | | trying to process the value of the ds-cfg-identity-mapper attribute in \ |
| | | configuration entry %s to determine which identity mapper should be used in \ |
| | | conjunction with the PLAIN SASL mechanism: %s |
| | | MILD_ERR_SASLPLAIN_CANNOT_MAP_USERNAME_325=An error occurred while attempting \ |
| | | to map username %s to a Directory Server entry: %s |
| | | INFO_SASLPLAIN_UPDATED_IDENTITY_MAPPER_326=Attribute \ |
| | | ds-cfg-identity-mapper in configuration entry %s has been updated. The \ |
| | | identity mapper defined in configuration entry %s will now be used to map \ |
| | | usernames to entries when processing SASL PLAIN bind requests |
| | | MILD_ERR_EXTOP_CANCEL_NO_REQUEST_VALUE_327=Unable to process the cancel \ |
| | | request because the extended operation did not include a request value |
| | | MILD_ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUE_328=An error occurred while \ |
| | |
| | | result of receiving a cancel request (message ID %d) |
| | | MILD_ERR_PWSCHEME_DOES_NOT_SUPPORT_AUTH_PASSWORD_330=Password storage scheme \ |
| | | %s does not support use with the authentication password attribute syntax |
| | | INFO_PWLENGTHVALIDATOR_DESCRIPTION_MIN_LENGTH_331=Minimum \ |
| | | number of characters that a password will be allowed to have. A value of \ |
| | | zero indicates that there is no minimum length. Changes to this \ |
| | | configuration attribute will take effect immediately |
| | | MILD_ERR_PWLENGTHVALIDATOR_CANNOT_DETERMINE_MIN_LENGTH_332=An error occurred \ |
| | | while attempting to determine the minimum allowed password length from the \ |
| | | ds-cfg-min-password-length attribute: %s |
| | | INFO_PWLENGTHVALIDATOR_DESCRIPTION_MAX_LENGTH_333=Maximum \ |
| | | number of characters that a password will be allowed to have. A value of \ |
| | | zero indicates that there is no maximum length. Changes to this \ |
| | | configuration attribute will take effect immediately |
| | | MILD_ERR_PWLENGTHVALIDATOR_CANNOT_DETERMINE_MAX_LENGTH_334=An error occurred \ |
| | | while attempting to determine the maximum allowed password length from the \ |
| | | ds-cfg-max-password-length attribute: %s |
| | | MILD_ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAX_335=The configured minimum \ |
| | | password length of %d characters is greater than the configured maximum \ |
| | | password length of %d |
| | |
| | | than the minimum required length of %d characters |
| | | MILD_ERR_PWLENGTHVALIDATOR_TOO_LONG_337=The provided password is longer than \ |
| | | the maximum allowed length of %d characters |
| | | INFO_PWLENGTHVALIDATOR_UPDATED_MIN_LENGTH_338=The minimum password length has \ |
| | | been updated to %d |
| | | INFO_PWLENGTHVALIDATOR_UPDATED_MAX_LENGTH_339=The maximum password length has \ |
| | | been updated to %d |
| | | INFO_RANDOMPWGEN_DESCRIPTION_CHARSET_340=Character set(s) that \ |
| | | should be used to generate the passwords. Each character set should be given \ |
| | | a name (consisting of only ASCII alphabetic characters) followed immediately \ |
| | | by a colon and the set of characters that should be included in that \ |
| | | character set. Changes to this configuration attribute will take effect \ |
| | | immediately |
| | | MILD_ERR_RANDOMPWGEN_NO_CHARSETS_341=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 \ |
| | |
| | | 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 |
| | | INFO_RANDOMPWGEN_DESCRIPTION_PWFORMAT_344=Format that should be \ |
| | | used for passwords constructed by this password generator. The 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. Changes to this configuration attribute will \ |
| | | take effect immediately |
| | | MILD_ERR_RANDOMPWGEN_NO_PWFORMAT_345=Configuration entry "%s" does not \ |
| | | contain attribute ds-cfg-password-format which specifies the format to use \ |
| | | for the generated password. This is a required attribute |
| | | MILD_ERR_RANDOMPWGEN_UNKNOWN_CHARSET_346=The password format string "%s" \ |
| | | references an undefined character set "%s" |
| | | MILD_ERR_RANDOMPWGEN_INVALID_PWFORMAT_347=The password format string "%s" \ |
| | |
| | | attempting to decode the value for configuration attribute \ |
| | | ds-cfg-password-format, which is used to specify the format for the generated \ |
| | | passwords: %s |
| | | INFO_SASLGSSAPI_DESCRIPTION_IDENTITY_MAPPER_DN_349=DN of the \ |
| | | configuration entry that holds the configuration for the identity mapper that \ |
| | | should be used to map the GSSAPI principal to a Directory Server user entry. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | MILD_ERR_SASLGSSAPI_NO_IDENTITY_MAPPER_ATTR_350=Configuration entry %s does \ |
| | | not contain attribute ds-cfg-identity-mapper which specifies the DN of the \ |
| | | identity mapper to use in conjunction with the GSSAPI SASL mechanism. This \ |
| | | is a required attribute |
| | | MILD_ERR_SASLGSSAPI_NO_SUCH_IDENTITY_MAPPER_351=The identity mapper %s \ |
| | | specified in attribute ds-cfg-identity-mapper of configuration entry %s \ |
| | | does not reference a valid identity mapper configuration that is enabled for \ |
| | | use in the Directory Server |
| | | MILD_ERR_SASLGSSAPI_CANNOT_GET_IDENTITY_MAPPER_352=An error occurred while \ |
| | | trying to process the value of the ds-cfg-identity-mapper attribute in \ |
| | | configuration entry %s to determine which identity mapper should be used in \ |
| | | conjunction with the GSSAPI SASL mechanism: %s |
| | | INFO_SASLGSSAPI_UPDATED_IDENTITY_MAPPER_353=Attribute \ |
| | | ds-cfg-identity-mapper in configuration entry %s has been updated. The \ |
| | | value "%s" will now be used as the DN of the identity mapper configuration \ |
| | | entry for GSSAPI authentication |
| | | MILD_ERR_EXTOP_PASSMOD_CANNOT_GET_PW_POLICY_354=An error occurred while \ |
| | | attempting to get the password policy for user %s: %s |
| | | MILD_ERR_EXTOP_PASSMOD_REQUIRE_CURRENT_PW_355=The current password must be \ |
| | |
| | | string "%s" could not be mapped to any user in the directory |
| | | MILD_ERR_EXTOP_PASSMOD_ERROR_MAPPING_USER_371=An error occurred while \ |
| | | attempting to map authorization ID string "%s" to a user entry: %s |
| | | INFO_ERRORLOG_ACCTNOTHANDLER_DESCRIPTION_NOTIFICATION_TYPES_372=Status \ |
| | | notification types for which log messages should be generated. It is \ |
| | | a multivalued attribute, and changes will take effect immediately |
| | | MILD_ERR_ERRORLOG_ACCTNOTHANDLER_INVALID_TYPE_373=Configuration entry %s \ |
| | | contains unrecognized account status notification type %s |
| | | MILD_ERR_ERRORLOG_ACCTNOTHANDLER_CANNOT_GET_NOTIFICATION_TYPES_374=An error \ |
| | | occurred while attempting to determine the account status notification types \ |
| | | from configuration entry %s: %s |
| | | NOTICE_ERRORLOG_ACCTNOTHANDLER_NOTIFICATION_375=Account-Status-Notification \ |
| | | type='%s' userdn='%s' id=%d msg='%s' |
| | | |
| | |
| | | MILD_ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITY_378=An error occurred while \ |
| | | attempting to verify the password for user %s during SASL PLAIN \ |
| | | authentication: %s |
| | | MILD_ERR_STARTTLS_ERROR_SENDING_CLEAR_RESPONSE_379=An unexpected error \ |
| | | occurred while attempting to send the clear-text response to the client after \ |
| | | starting TLS negotiation: %s |
| | | MILD_WARN_EXTOP_PASSMOD_NOOP_380=The password modify operation was not \ |
| | | actually performed in the Directory Server because the LDAP no-op control was \ |
| | | present in the request |
| | |
| | | privileges to perform password reset operations |
| | | MILD_ERR_SASLDIGESTMD5_EMPTY_AUTHZID_393=The provided authorization ID was \ |
| | | empty, which is not allowed for DIGEST-MD5 authentication |
| | | MILD_ERR_SASLDIGESTMD5_AUTHZID_INVALID_DN_394=The provided authorization ID \ |
| | | %s contained an invalid DN: %s |
| | | MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_SUCH_ENTRY_396=The entry %s specified as \ |
| | | the authorization identity does not exist |
| | | MILD_ERR_SASLDIGESTMD5_AUTHZID_CANNOT_GET_ENTRY_397=The entry %s specified as \ |
| | | the authorization identity could not be retrieved: %s |
| | | MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_MAPPED_ENTRY_398=The server was unable to \ |
| | | find any entry corresponding to authorization ID %s |
| | | MILD_ERR_SASLDIGESTMD5_CANNOT_MAP_AUTHZID_399=An error occurred while \ |
| | | attempting to map authorization ID %s to a user entry: %s |
| | | MILD_ERR_SASLPLAIN_AUTHZID_INVALID_DN_400=The provided authorization ID %s \ |
| | | contained an invalid DN: %s |
| | | MILD_ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGES_401=The authenticating \ |
| | |
| | | authorization ID %s was found in the server |
| | | MILD_ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZID_405=An error occurred while \ |
| | | attempting to map authorization ID %s to a user entry: %s |
| | | INFO_SASLEXTERNAL_DESCRIPTION_CERT_MAPPER_DN_406=DN of the \ |
| | | configuration entry that defines the certificate mapper to use when mapping a \ |
| | | certificate to a user entry. Changes to this configuration attribute will \ |
| | | take effect immediately |
| | | MILD_ERR_SASLEXTERNAL_NO_CERTIFICATE_MAPPER_DN_407=Configuration entry %s \ |
| | | does not contain attribute ds-cfg-certificate-mapper which is required to \ |
| | | specify which certificate mapper should be used to map certificates to user \ |
| | | entries |
| | | MILD_ERR_SASLEXTERNAL_INVALID_CERTIFICATE_MAPPER_DN_408=Configuration entry \ |
| | | %s contains a certificate mapper DN of %s, but no such certificate mapper is \ |
| | | enabled for use in the Directory Server |
| | | MILD_ERR_SASLEXTERNAL_CANNOT_GET_CERT_MAPPER_DN_409=An error occurred while \ |
| | | attempting to retrieve the certificate mapper DN from configuration entry %s: \ |
| | | %s |
| | | INFO_SASLEXTERNAL_UPDATED_CERT_MAPPER_DN_410=Attribute \ |
| | | ds-cfg-certificate-mapper in configuration entry %s has been updated. \ |
| | | Certificate mapper %s will now be used to map certificates to user entries |
| | | INFO_SDTUACM_DESCRIPTION_SUBJECT_ATTR_411=Name of the attribute \ |
| | | type in user entries that contains the subjects of the certificates held by \ |
| | | that user. Changes to this configuration attribute will take effect \ |
| | | immediately |
| | | SEVERE_ERR_SDTUACM_NO_SUBJECT_ATTR_412=Configuration entry %s does not \ |
| | | contain required attribute %s, which is used to specify which attribute \ |
| | | should contain the subjects of the certificates held by users |
| | | SEVERE_ERR_SDTUACM_NO_SUCH_ATTR_413=Configuration entry %s indicates that \ |
| | | certificate subjects should be held in attribute %s, but this attribute is \ |
| | | not defined in the server schema |
| | | SEVERE_ERR_SDTUACM_CANNOT_GET_SUBJECT_ATTR_414=An error occurred while \ |
| | | attempting to determine which attribute type should be used to hold \ |
| | | certificate subjects from configuration entry %s: %s |
| | | INFO_SDTUACM_DESCRIPTION_BASE_DN_415=Base DNs below which the \ |
| | | searches to find matching user entries will be performed. If no base DN(s) \ |
| | | are provided, then the server will search below all public naming contexts. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | SEVERE_ERR_SDTUACM_CANNOT_GET_BASE_DN_416=An error occurred while attempting \ |
| | | to determine the search base DN(s) from configuration entry %s: %s |
| | | SEVERE_ERR_SDTUACM_NO_PEER_CERTIFICATE_417=Could not map the provided \ |
| | | certificate chain to a user entry because no peer certificate was available |
| | | SEVERE_ERR_SDTUACM_PEER_CERT_NOT_X509_418=Could not map the provided \ |
| | |
| | | certificate (peer certificate format was %s) |
| | | SEVERE_ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_419=The certificate with subject \ |
| | | %s could not be mapped to exactly one user. It maps to both %s and %s |
| | | INFO_SATUACM_DESCRIPTION_ATTR_MAP_420=Name of the attribute \ |
| | | type in user entries that defines the mapping between attributes in \ |
| | | certificate subjects and attributes in user entries. Values should be in the \ |
| | | form 'certattr:userattr'. Changes to this configuration attribute will take \ |
| | | effect immediately |
| | | SEVERE_ERR_SATUACM_NO_MAP_ATTR_421=Configuration entry %s does not contain \ |
| | | required attribute %s, which is used to specify the mappings between \ |
| | | attributes in certificate subjects and attributes in user entries |
| | | SEVERE_ERR_SATUACM_INVALID_MAP_FORMAT_422=Configuration entry %s has value \ |
| | | '%s' which violates the format required for attribute mappings. The expected \ |
| | | format is 'certattr:userattr' |
| | |
| | | references attribute %s which is not defined in the server schema |
| | | SEVERE_ERR_SATUACM_DUPLICATE_USER_ATTR_425=Configuration entry %s contains \ |
| | | multiple mappings for user attribute %s |
| | | SEVERE_ERR_SATUACM_CANNOT_GET_ATTR_MAP_426=An error occurred while attempting \ |
| | | to determine the set of attribute mappings from configuration entry %s: %s |
| | | INFO_SATUACM_DESCRIPTION_BASE_DN_427=Base DNs below which the \ |
| | | searches to find matching user entries will be performed. If no base DN(s) \ |
| | | are provided, then the server will search below all public naming contexts. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | SEVERE_ERR_SATUACM_CANNOT_GET_BASE_DN_428=An error occurred while attempting \ |
| | | to determine the search base DN(s) from configuration entry %s: %s |
| | | SEVERE_ERR_SATUACM_NO_PEER_CERTIFICATE_429=Could not map the provided \ |
| | | certificate chain to a user entry because no peer certificate was available |
| | | SEVERE_ERR_SATUACM_PEER_CERT_NOT_X509_430=Could not map the provided \ |
| | |
| | | does not contain any attributes for which a mapping has been established |
| | | SEVERE_ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_433=The certificate with subject \ |
| | | %s could not be mapped to exactly one user. It maps to both %s and %s |
| | | INFO_FCM_DESCRIPTION_FINGERPRINT_ATTR_434=Name of the attribute \ |
| | | type in user entries that contains the fingerprints of the certificates held \ |
| | | by that user. Changes to this configuration attribute will take effect \ |
| | | immediately |
| | | SEVERE_ERR_FCM_NO_FINGERPRINT_ATTR_435=Configuration entry %s does not \ |
| | | contain required attribute %s, which is used to specify which attribute \ |
| | | should contain the fingerprints of the certificates held by users |
| | | SEVERE_ERR_FCM_NO_SUCH_ATTR_436=Configuration entry %s indicates that \ |
| | | certificate fingerprints should be held in attribute %s, but this attribute \ |
| | | is not defined in the server schema |
| | | SEVERE_ERR_FCM_CANNOT_GET_FINGERPRINT_ATTR_437=An error occurred while \ |
| | | attempting to determine which attribute type should be used to hold \ |
| | | certificate fingerprints from configuration entry %s: %s |
| | | INFO_FCM_DESCRIPTION_FINGERPRINT_ALGORITHM_438=Name of the \ |
| | | digest algorithm used for the certificate fingerprints. The value should be \ |
| | | either 'MD5' or 'SHA1'. Changes to this configuration attribute will take \ |
| | | effect immediately |
| | | SEVERE_ERR_FCM_NO_FINGERPRINT_ALGORITHM_439=Configuration entry %s does not \ |
| | | contain required attribute %s, which is used to specify which digest \ |
| | | algorithm should be used to compute certificate fingerprints |
| | | SEVERE_ERR_FCM_CANNOT_GET_FINGERPRINT_ALGORITHM_440=An error occurred while \ |
| | | attempting to determine the digest algorithm from configuration entry %s: %s |
| | | INFO_FCM_DESCRIPTION_BASE_DN_441=Base DNs below which the \ |
| | | searches to find matching user entries will be performed. If no base DN(s) \ |
| | | are provided, then the server will search below all public naming contexts. \ |
| | | Changes to this configuration attribute will take effect immediately |
| | | SEVERE_ERR_FCM_CANNOT_GET_BASE_DN_442=An error occurred while attempting to \ |
| | | determine the search base DN(s) from configuration entry %s: %s |
| | | SEVERE_ERR_FCM_NO_PEER_CERTIFICATE_443=Could not map the provided certificate \ |
| | | chain to a user entry because no peer certificate was available |
| | | SEVERE_ERR_FCM_PEER_CERT_NOT_X509_444=Could not map the provided certificate \ |
| | |
| | | SEVERE_ERR_DYNAMICGROUP_CANNOT_RETURN_ENTRY_452=The server encountered a \ |
| | | timeout while attempting to add user %s to the member list for dynamic group \ |
| | | %s |
| | | INFO_PWDIFFERENCEVALIDATOR_DESCRIPTION_MIN_DIFFERENCE_453=Minimum \ |
| | | difference that a password will be allowed to have. A value of zero \ |
| | | indicates that there is no minimum difference. Changes to this configuration \ |
| | | attribute will take effect immediately |
| | | MILD_ERR_PWDIFFERENCEVALIDATOR_CANNOT_DETERMINE_MIN_DIFFERENCE_454=An error \ |
| | | occurred while attempting to determine the minimum allowed password \ |
| | | difference from the ds-cfg-min-password-difference attribute: %s |
| | | INFO_PWDIFFERENCEVALIDATOR_UPDATED_MIN_DIFFERENCE_455=The minimum password \ |
| | | difference has been updated to %d |
| | | MILD_ERR_PWDIFFERENCEVALIDATOR_TOO_SMALL_456=The provided password differs \ |
| | | less than the minimum required difference of %d characters |
| | | MILD_ERR_REPEATEDCHARS_VALIDATOR_TOO_MANY_CONSECUTIVE_457=The provided \ |
| | |
| | | attempting to update the password policy state information for user %s as \ |
| | | part of a password modify extended operation (result code='%s', error \ |
| | | message='%s') |
| | | MILD_ERR_SASLDIGESTMD5_INVALID_DIGEST_URI_529=The DIGEST-MD5 credentials \ |
| | | provided by the client requested an invalid digest URI of %s. The expected \ |
| | | digest URI was %s |
| | | MILD_ERR_EXTOP_PASSMOD_PW_IN_HISTORY_530=The provided new password was \ |
| | | already contained in the password history |
| | | MILD_ERR_SMTPALERTHANDLER_NO_SMTP_SERVERS_531=The Directory Server is not \ |
| | |
| | | message %s: %s |
| | | MILD_ERR_REGEXMAP_INVALID_MATCH_PATTERN_533=The provided match pattern "%s" \ |
| | | could not be parsed as a regular expression: %s |
| | | MILD_ERR_REGEXMAP_UNKNOWN_ATTR_534=Configuration entry %s contains value %s \ |
| | | for attribute ds-cfg-match-attribute but that is not a valid name or OID for \ |
| | | any attribute type defined in the Directory Server schema |
| | | MILD_ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_535=The processed ID string %s \ |
| | | mapped to multiple users |
| | | MILD_ERR_REGEXMAP_INEFFICIENT_SEARCH_536=The internal search based on \ |
| | |
| | | decrypt a value using password storage scheme %s: %s |
| | | MILD_ERR_GET_SYMMETRIC_KEY_NO_VALUE_561=Cannot decode the provided \ |
| | | symmetric key extended operation because it does not have a value |
| | | MILD_ERR_GET_SYMMETRIC_KEY_INVALID_TYPE_562=Cannot decode the provided \ |
| | | symmetric key extended operation because the value sequence has an element \ |
| | | with an invalid type of %s |
| | | MILD_ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTION_563=Cannot decode the \ |
| | | provided symmetric key extended request: %s |
| | | MILD_ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTION_564=An unexpected error occurred \ |
| | |
| | | SEVERE_ERR_REGEXMAP_ATTR_UNINDEXED_566=The regular expression identity mapper \ |
| | | defined in configuration entry %s references attribute type %s which is does \ |
| | | not have an equality index defined in backend %s |
| | | SEVERE_ERR_FCM_ATTR_UNINDEXED_567=The fingerprint certificate mapper defined \ |
| | | in configuration entry %s references attribute type %s which is does not \ |
| | | have an equality index defined in backend %s |
| | | SEVERE_WARN_SATUACM_ATTR_UNINDEXED_568=The subject attribute to user attribute \ |
| | | certificate mapper defined in configuration entry %s references attribute \ |
| | | type %s which is does not have an equality index defined in backend %s |
| | | SEVERE_ERR_SDTUACM_ATTR_UNINDEXED_569=The subject DN to user attribute \ |
| | | certificate mapper defined in configuration entry %s references attribute \ |
| | | type %s which is does not have an equality index defined in backend %s |
| | | SEVERE_ERR_SASLDIGESTMD5_PROTOCOL_ERROR_570=SASL DIGEST MD5 protocol error: %s |
| | | NOTICE_LOG_EXTENSION_INFORMATION_571=Loaded extension from file '%s' (build %s, \ |
| | | revision %s) |
| | | SEVERE_ERR_SASL_CREATE_SASL_SERVER_FAILED_572=Failed to create a SASL server \ |