mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git
opendj-sdk/opends/src/messages/messages/extension_fr.properties
@@ -21,14 +21,10 @@ # CDDL HEADER END # # Copyright 2006-2008 Sun Microsystems, Inc. # # Global directives # global.category=EXTENSIONS # # Format string definitions # @@ -47,25 +43,41 @@ # # ORDINAL is an integer unique among other ordinals in this file # SEVERE_ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGEST_1=An error occurred while attempting to initialize the message digest generator for the %s algorithm: %s ###SEVERE_ERR_PWSCHEME_CANNOT_INITIALIZE_MESSAGE_DIGEST_1=An error occurred \ ### while attempting to initialize the message digest generator for the %s \ ### algorithm: %s MILD_ERR_PWSCHEME_CANNOT_BASE64_DECODE_STORED_PASSWORD_2=Une erreur s'est produite lors du d\u00e9codage en base64 de la valeur de mot de passe %s\u00a0: %s MILD_ERR_PWSCHEME_NOT_REVERSIBLE_3=Le sch\u00e9ma de stockage de mot de passe %s n'\u00e9tant pas r\u00e9versible, il est impossible de r\u00e9cup\u00e9rer la version en texte brut d'un mot de passe cod\u00e9 MILD_ERR_JMX_ALERT_HANDLER_CANNOT_REGISTER_4=Une erreur est survenue lors de l'enregistrement du gestionnaire d'alertes JMX aupr\u00e8s du serveur MBean\u00a0: %s MILD_ERR_PWSCHEME_CANNOT_ENCODE_PASSWORD_5=Une erreur inattendue s'est produite lors du codage d'un mot de passe \u00e0 l'aide du sch\u00e9ma de stockage d\u00e9fini dans la classe %s\u00a0: %s SEVERE_ERR_CACHE_INVALID_INCLUDE_FILTER_6=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 SEVERE_ERR_CACHE_INVALID_EXCLUDE_FILTER_7=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 FATAL_ERR_FIFOCACHE_CANNOT_INITIALIZE_8=A fatal error occurred while trying to initialize fifo entry cache: %s FATAL_ERR_SOFTREFCACHE_CANNOT_INITIALIZE_9=A fatal error occurred while trying to initialize soft reference entry cache: %s ###SEVERE_ERR_CACHE_INVALID_INCLUDE_FILTER_6=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 ###SEVERE_ERR_CACHE_INVALID_EXCLUDE_FILTER_7=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 ###FATAL_ERR_FIFOCACHE_CANNOT_INITIALIZE_8=A fatal error occurred while trying \ ### to initialize fifo entry cache: %s ###FATAL_ERR_SOFTREFCACHE_CANNOT_INITIALIZE_9=A fatal error occurred while \ ### trying to initialize soft reference entry cache: %s NOTICE_CACHE_PRELOAD_PROGRESS_START_10=D\u00e9marrage du pr\u00e9chargement du cache d'entr\u00e9e pour le backend %s NOTICE_CACHE_PRELOAD_PROGRESS_REPORT_11=Le pr\u00e9chargement du cache d'entr\u00e9e pour le backend %s a trait\u00e9 %d entr\u00e9es, %d Mo de m\u00e9moire de segments libres disponibles NOTICE_CACHE_PRELOAD_PROGRESS_DONE_12=Le pr\u00e9chargement du cache d'entr\u00e9e pour le backend %s est termin\u00e9, avec un total de %d entr\u00e9es trait\u00e9es SEVERE_WARN_CACHE_PRELOAD_INTERRUPTED_13=The entry cache preload for %s backend has been interrupted SEVERE_WARN_CACHE_PRELOAD_BACKEND_FAILED_14=The entry cache preload is not supported by %s backend, and as a result no entries from this backend will be preloaded into the entry cache SEVERE_ERR_CACHE_PRELOAD_ENTRY_FAILED_15=Failed to preload %s entry into the entry cache: %s ###SEVERE_WARN_CACHE_PRELOAD_INTERRUPTED_13=The entry cache preload for %s \ ### backend has been interrupted ###SEVERE_WARN_CACHE_PRELOAD_BACKEND_FAILED_14=The entry cache preload is not \ ### supported by %s backend, and as a result no entries from this backend will \ ### 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=La s\u00e9quence de requ\u00eate \u00e9tendue de modification de mot de passe inclut un \u00e9l\u00e9ment ASN.1 de type non valide\u00a0: %s MILD_ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUEST_33=Une erreur inattendue s'est produite lors du d\u00e9codage de la s\u00e9quence de requ\u00eate \u00e9tendue de modification de mot de passe\u00a0: %s MILD_ERR_EXTOP_PASSMOD_NO_AUTH_OR_USERID_34=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car elle ne contient pas d'ID d'autorisation et la connexion sous-jacente n'est pas authentifi\u00e9e SEVERE_ERR_EXTOP_PASSMOD_CANNOT_LOCK_USER_ENTRY_35=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 ###SEVERE_ERR_EXTOP_PASSMOD_CANNOT_LOCK_USER_ENTRY_35=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 MILD_ERR_EXTOP_PASSMOD_CANNOT_DECODE_AUTHZ_DN_36=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car le serveur ne peut pas d\u00e9coder "%s" comme DN valide \u00e0 utiliser dans l'ID d'autorisation pour l'op\u00e9ration MILD_ERR_EXTOP_PASSMOD_INVALID_AUTHZID_STRING_37=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car elle contient un champ userIdentity non valide. La cha\u00eene userIdentity fournie est "%s" MILD_ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZID_38=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car il est impossible d'identifier l'entr\u00e9e utilisateur \u00e0 mettre \u00e0 jour en fonction de l'autorisation DN de "%s" @@ -73,69 +85,171 @@ MILD_ERR_EXTOP_PASSMOD_MULTIPLE_ENTRIES_BY_AUTHZID_40=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car l'UID d'autorisation "%s" fournie correspond \u00e0 plusieurs entr\u00e9es du r\u00e9pertoire MILD_ERR_EXTOP_PASSMOD_INVALID_OLD_PASSWORD_41=Impossible de traiter la requ\u00eate \u00e9tendue de modification de mot de passe car le mot de passe actuel fourni \u00e0 l'utilisateur n'est pas valide INFO_FILE_KEYMANAGER_DESCRIPTION_FILE_43=Chemin du fichier contenant les informations keystore Directory Server. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Type de keystore pour le keystore Directory Server. Les valeurs valides doivent toujours inclure 'JKS' et 'PKCS12' mais des impl\u00e9mentations diff\u00e9rentes peuvent accepter \u00e9galement d'autres valeurs. Si aucune valeur n'est fournie, la valeur JVM par d\u00e9faut est utilis\u00e9e. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Le nom de la propri\u00e9t\u00e9 Java contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Nom de la variable d'environnement contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Chemin vers le fichier texte dont le contenu doit \u00eatre une ligne unique contenant le num\u00e9ro d'identification personnel en texte clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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_CANNOT_READ_57=An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s 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 SEVERE_ERR_FILE_KEYMANAGER_NO_PIN_61=Configuration entry %s does not specify a means of determining the PIN needed to access the contents of the file-based key manager. The PIN may be specified in a Java property (named by attribute ds-cfg-key-store-pin-property), an environment variable (named by attribute ds-cfg-key-store-pin-environment-variable), a text file (named by attribute ds-cfg-key-store-pin-file), or directly in the entry using attribute ds-cfg-key-store-pin SEVERE_ERR_FILE_KEYMANAGER_CANNOT_LOAD_62=An error occurred while trying to 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 ###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_CANNOT_READ_57=An error occurred while \ ### trying to read the keystore PIN from file %s specified in configuration \ ### attribute ds-cfg-key-store-pin-file of configuration entry %s: %s ###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 ###SEVERE_ERR_FILE_KEYMANAGER_NO_PIN_61=Configuration entry %s does not specify \ ### a means of determining the PIN needed to access the contents of the \ ### file-based key manager. The PIN may be specified in a Java property (named \ ### by attribute ds-cfg-key-store-pin-property), an environment variable (named \ ### by attribute ds-cfg-key-store-pin-environment-variable), a text file (named \ ### by attribute ds-cfg-key-store-pin-file), or directly in the entry using \ ### attribute ds-cfg-key-store-pin ###SEVERE_ERR_FILE_KEYMANAGER_CANNOT_LOAD_62=An error occurred while trying to \ ### 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=La valeur de l'attribut ds-cfg-key-store-file de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %s. Cette nouvelle valeur prendra effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s INFO_FILE_KEYMANAGER_UPDATED_TYPE_65=La valeur de l'attribut ds-cfg-key-store-type de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mise \u00e0 jour \u00e0 %s. Cette nouvelle valeur prendra effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s INFO_FILE_KEYMANAGER_UPDATED_PIN_66=Le num\u00e9ro d'identification personnel utilis\u00e9 pour acc\u00e9der au gestionnaire de cl\u00e9s bas\u00e9 sur fichier a \u00e9t\u00e9 mis \u00e0 jour. La nouvelle valeur prendra effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_PROPERTY_67=Nom de la propri\u00e9t\u00e9 Java contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s PKCS#11. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Nom de la variable d'environnement contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s PKCS#11. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Chemin vers le fichier texte dont le contenu doit \u00eatre une ligne unique contenant le num\u00e9ro d'identification personnel en texte clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s PKCS#11. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 exist SEVERE_ERR_PKCS11_KEYMANAGER_PIN_FILE_CANNOT_READ_75=An error occurred while trying to read the keystore PIN from file %s specified in configuration attribute ds-cfg-key-store-pin-file of configuration entry %s: %s 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 ###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 \ ### exist ###SEVERE_ERR_PKCS11_KEYMANAGER_PIN_FILE_CANNOT_READ_75=An error occurred while \ ### trying to read the keystore PIN from file %s specified in configuration \ ### attribute ds-cfg-key-store-pin-file of configuration entry %s: %s ###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=Num\u00e9ro d'identification personnel en texte clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire de cl\u00e9s PKCS#11. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 SEVERE_ERR_PKCS11_KEYMANAGER_NO_PIN_80=Configuration entry %s does not specify a means of determining the PIN needed to access the contents of the PKCS#11 key manager. The PIN may be specified in a Java property (named by attribute ds-cfg-key-store-pin-property), an environment variable (named by attribute ds-cfg-key-store-pin-environment-variable), a text file (named by attribute ds-cfg-key-store-pin-file), or directly in the entry using 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 ###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 ###SEVERE_ERR_PKCS11_KEYMANAGER_NO_PIN_80=Configuration entry %s does not \ ### specify a means of determining the PIN needed to access the contents of the \ ### PKCS#11 key manager. The PIN may be specified in a Java property (named by \ ### attribute ds-cfg-key-store-pin-property), an environment variable (named by \ ### attribute ds-cfg-key-store-pin-environment-variable), a text file (named by \ ### attribute ds-cfg-key-store-pin-file), or directly in the entry using \ ### 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=Le num\u00e9ro d'identification personnel utilis\u00e9 pour acc\u00e9der au gestionnaire de cl\u00e9s PKCS#11 a \u00e9t\u00e9 mis \u00e0 jour. La nouvelle valeur prendra effet \u00e0 la prochaine ouverture du gestionnaire de cl\u00e9s 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 ###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=Chemin vers le fichier contenant les informations du magasin d'approbations Directory Server. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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 ###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=Type de keystore pour le magasin d'approbations de Directory Server. Les valeurs valides doivent toujours inclure 'JKS' et 'PKCS12', mais des impl\u00e9mentations diff\u00e9rentes peuvent accepter d'autres valeurs. Si aucune valeur n'est fournie, la valeur JVM par d\u00e9faut est utilis\u00e9e. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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 ###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=Le nom de la propri\u00e9t\u00e9 Java contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire d'approbations bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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=Nom de la variable d'environnement contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire d'approbations bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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 ###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=Nom de la variable d'environnement contenant le num\u00e9ro d'identification personnel en texte en clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire d'approbations bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbation ###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=Chemin vers le fichier texte dont le contenu doit \u00eatre une ligne unique contenant le num\u00e9ro d'identification personnel en texte clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire d'approbations bas\u00e9 sur fichier. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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 does not exist SEVERE_ERR_FILE_TRUSTMANAGER_PIN_FILE_CANNOT_READ_99=An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s SEVERE_ERR_FILE_TRUSTMANAGER_PIN_FILE_EMPTY_100=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 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 ###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 \ ### does not exist ###SEVERE_ERR_FILE_TRUSTMANAGER_PIN_FILE_CANNOT_READ_99=An error occurred while \ ### trying to read the trust store PIN from file %s specified in configuration \ ### attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s ###SEVERE_ERR_FILE_TRUSTMANAGER_PIN_FILE_EMPTY_100=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 \ ### 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=Num\u00e9ro d'identification personnel en texte clair n\u00e9cessaire \u00e0 l'ouverture du gestionnaire d'approbations. Les modifications de cet attribut de configuration prendront effet \u00e0 la prochaine ouverture du gestionnaire d'approbations 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 while trying to create a trust manager factory to access the contents of trust store file %s: %s 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 ###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 \ ### while trying to create a trust manager factory to access the contents of \ ### trust store file %s: %s ###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=La valeur de l'attribut ds-cfg-trust-store-file dans l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %s. La nouvelle valeur prendra effet lors de la prochaine ouverture du gestionnaire d'approbations INFO_FILE_TRUSTMANAGER_UPDATED_TYPE_108=La valeur de l'attribut ds-cfg-trust-store-type dans l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %s. Cette nouvelle valeur prendra effet lors de la prochaine ouverture du gestionnaire d'approbations INFO_FILE_TRUSTMANAGER_UPDATED_PIN_109=Le num\u00e9ro d'identification personnel utilis\u00e9 pour acc\u00e9der au gestionnaire d'approbations bas\u00e9 sur fichier a \u00e9t\u00e9 mis \u00e0 jour. La nouvelle valeur prendra effet \u00e0 la prochaine ouverture du gestionnaire d'approbations @@ -152,22 +266,42 @@ MILD_ERR_STARTTLS_NO_CLIENT_CONNECTION_128=Impossible d'utiliser StartTLS sur cette connexion car la connexion client sous-jacente n'est pas disponible MILD_ERR_STARTTLS_NOT_TLS_CAPABLE_129=Impossible d'utiliser StartTLS sur cette connexion client car ce type de connexion ne prend pas en charge StartTLS pour prot\u00e9ger ses communications MILD_ERR_STARTTLS_ERROR_ON_ENABLE_130=Une erreur inattendue s'est produite lors de l'activation du gestionnaire de s\u00e9curit\u00e9 de la connexion TLS sur la connexion client \u00e0 des fins d'utilisation de StartTLS\u00a0: %s INFO_SASLEXTERNAL_DESCRIPTION_VALIDATION_POLICY_131=Indique si le gestionnaire de m\u00e9canisme SASL EXTERNAL doit tenter de valider le certificat de pair en fonction d'un certificat de l'entr\u00e9e utilisateur correspondante. La valeur doit \u00eatre "true" (tente toujours de valider le certificat et \u00e9choue en cas d'absence de certificat), "false" (ne tente jamais de valider le certificat de pair) et "ifpresent" (valide le certificat de pair s'il existe un ou plusieurs certificats dans l'entr\u00e9e utilisateur, mais n'\u00e9choue pas s'il n'en existe aucun. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=Nom de l'attribut contenant les informations de certificat dans les entr\u00e9es utilisateur \u00e0 des fins de validation. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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 INFO_SASLEXTERNAL_DESCRIPTION_VALIDATION_POLICY_131=Indique si le gestionnaire de m\u00e9canisme SASL EXTERNAL doit tenter de valider le certificat de pair en fonction d'un certificat de l'entr\u00e9e utilisateur correspondante. La valeur doit \u00eatre "true" (tente toujours de valider le certificat et \u00e9choue en cas d'absence de certificat), "false" (ne tente jamais de valider le certificat de pair) et "ifpresent" (valide le certificat de pair s'il existe un ou plusieurs certificats dans l'entr\u00e9e utilisateur, mais n'\u00e9choue pas s'il n'en existe aucun. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=Nom de l'attribut contenant les informations de certificat dans les entr\u00e9es utilisateur \u00e0 des fins de validation. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=Authentification impossible via SASL EXTERNAL car l'entr\u00e9e utilisateur %s mapp\u00e9e ne poss\u00e8de pas de certificats permettant de v\u00e9rifier le certificat de pair pr\u00e9sent\u00e9 MILD_ERR_SASLEXTERNAL_PEER_CERT_NOT_FOUND_138=Authentification impossible via SASL EXTERNAL car l'entr\u00e9e utilisateur %s mapp\u00e9e ne contient pas le certificat de pair pr\u00e9sent\u00e9 par le client MILD_ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERT_139=Une erreur s'est produite lors de la validation du certificat de pair pr\u00e9sent\u00e9 par le client avec un certificat de l'entr\u00e9e de l'utilisateur %s\u00a0: %s INFO_SASLEXTERNAL_UPDATED_VALIDATION_POLICY_140=L'attribut ds-cfg-certificate-validation-policy de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. La nouvelle strat\u00e9gie de validation de certificat client est %s INFO_SASLEXTERNAL_UPDATED_CERT_ATTR_141=L'attribut ds-cfg-certificate-attribute de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. L'attribut %s sera d\u00e9sormais utilis\u00e9 lors de la validation de certificats de pair INFO_SASLPLAIN_DESCRIPTION_USERNAME_ATTRIBUTE_142=Nom de l'attribut \u00e0 utiliser pour identifier les entr\u00e9es utilisateur en fonction du param\u00e8tre authcID/authzID fourni lors de l'authentification SASL PLAIN. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=DN de base \u00e0 utiliser lors de la recherche d'entr\u00e9es en fonction du param\u00e8tre authcID/authzID fourni lors de l'authentification SASL PLAIN. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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 INFO_SASLPLAIN_DESCRIPTION_USERNAME_ATTRIBUTE_142=Nom de l'attribut \u00e0 utiliser pour identifier les entr\u00e9es utilisateur en fonction du param\u00e8tre authcID/authzID fourni lors de l'authentification SASL PLAIN. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=DN de base \u00e0 utiliser lors de la recherche d'entr\u00e9es en fonction du param\u00e8tre authcID/authzID fourni lors de l'authentification SASL PLAIN. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=L'authentification SASL PLAIN requiert des informations d'identification SASL, or aucune n'est incluse dans la requ\u00eate de liaison MILD_ERR_SASLPLAIN_NO_NULLS_IN_CREDENTIALS_148=La requ\u00eate de liaison SASL PLAIN n'inclut pas de caract\u00e8res NULL. Les caract\u00e8res NULL sont obligatoires comme d\u00e9limiteurs entre l'ID d'autorisation et l'ID d'authentification, ainsi qu'entre l'ID d'authentification et le mot de passe MILD_ERR_SASLPLAIN_NO_SECOND_NULL_149=La requ\u00eate de liaison SASL PLAIN n'inclut pas de second caract\u00e8re NULL, obligatoire comme d\u00e9limiteur entre l'ID d'authentification et le mot de passe dans les informations d'identification @@ -187,12 +321,22 @@ INFO_SASLPLAIN_CANNOT_LOCK_ENTRY_163=Impossible pour Directory Server d'obtenir un verrou de lecture pour l'entr\u00e9e utilisateur %s en vue de la r\u00e9cup\u00e9rer MILD_ERR_SEDCM_CANNOT_LOCK_ENTRY_164=Impossible pour Directory Server d'obtenir un verrou de lecture pour l'entr\u00e9e utilisateur %s en vue de la r\u00e9cup\u00e9rer INFO_SASLANONYMOUS_TRACE_165=L'op\u00e9ration de liaison SASL ANONYMOUS (conn=%d, op=%d) a fourni des informations de suivi\u00a0: %s 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=Nom de l'attribut \u00e0 utiliser pour identifier les entr\u00e9es utilisateur en fonction du nom d'utilisateur fourni lors de l'authentification SASL CRAM-MD5. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=DN de base \u00e0 utiliser lors de la recherche d'entr\u00e9es en fonction du nom d'utilisateur fourni lors de l'authentification SASL CRAM-MD5. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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 ###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=Nom de l'attribut \u00e0 utiliser pour identifier les entr\u00e9es utilisateur en fonction du nom d'utilisateur fourni lors de l'authentification SASL CRAM-MD5. Il doit sp\u00e9cifier le nom d'un type d'attribut valide d\u00e9fini dans le sch\u00e9ma de serveur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=DN de base \u00e0 utiliser lors de la recherche d'entr\u00e9es en fonction du nom d'utilisateur fourni lors de l'authentification SASL CRAM-MD5. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=La requ\u00eate de liaison SASL CRAM-MD5 contient des informations d'identification SASL mais aucune question/r\u00e9ponse n'est stock\u00e9e pour cette connexion client. La premi\u00e8re requ\u00eate de liaison SASL CRAM-MD5 du processus en deux \u00e9tapes ne doit pas contenir d'informations d'identification SASL client MILD_ERR_SASLCRAMMD5_INVALID_STORED_CHALLENGE_173=La requ\u00eate de liaison SASL CRAM-MD5 contient des informations d'identification SASL, mais le format des informations de statut SASL stock\u00e9es pour cette connexion client n'est pas appropri\u00e9 pour la question/r\u00e9ponse MILD_ERR_SASLCRAMMD5_NO_SPACE_IN_CREDENTIALS_174=La requ\u00eate de liaison SASL CRAM-MD5 du client inclut les informations d'identification SASL mais aucun espace ne s\u00e9pare le nom d'utilisateur du hachage d'authentification @@ -204,7 +348,7 @@ MILD_ERR_SASLCRAMMD5_CANNOT_GET_ENTRY_BY_DN_180=Une erreur s'est produite lors de la r\u00e9cup\u00e9ration de l'entr\u00e9e utilisateur %s tel que cela est sp\u00e9cifi\u00e9 dans le nom d'utilisateur bas\u00e9 sur DN d'une requ\u00eate de liaison SASL CRAM-MD5\u00a0: %s MILD_ERR_SASLCRAMMD5_ZERO_LENGTH_USERNAME_181=Le nom d'utilisateur contenu dans la requ\u00eate de liaison SASL CRAM-MD5 poss\u00e8de une longueur de z\u00e9ro caract\u00e8res, ce qui est interdit. L'authentification SASL CRAM-MD5 n'autorise pas l'utilisation d'une cha\u00eene vide comme mot de passe MILD_ERR_SASLCRAMMD5_CANNOT_PERFORM_INTERNAL_SEARCH_182=Une erreur s'est produite lors de la recherche interne destin\u00e9e \u00e0 r\u00e9cup\u00e9rer l'entr\u00e9e utilisateur associ\u00e9e au nom d'utilisateur SASL CRAM-MD5 %s. Le r\u00e9sultat de cette recherche donne %s avec un message de %s MILD_ERR_SASLCRAMMD5_MULTIPLE_MATCHING_ENTRIES_183=La recherche interne destin\u00e9e \u00e0 r\u00e9soudre le nom d'utilisateur SASL CRAM-MD5 %s correspond \u00e0 plusieurs entr\u00e9es. L'authentification ne peut pas r\u00e9ussir tant que le nom d'utilisateur est mapp\u00e9 \u00e0 une seule entr\u00e9e utilisateur MILD_ERR_SASLCRAMMD5_MULTIPLE_MATCHING_ENTRIES_183=La recherche interne destin\u00e9e \u00e0 r\u00e9soudre le nom d'utilisateur SASL CRAM-MD5 %s correspond \u00e0 plusieurs entr\u00e9es. L'authentification ne peut pas r\u00e9ussir tant que le nom d'utilisateur est mapp\u00e9 vers une seule entr\u00e9e utilisateur MILD_ERR_SASLCRAMMD5_NO_MATCHING_ENTRIES_184=Impossible au serveur de trouver des entr\u00e9es utilisateur pour le nom d'utilisateur fourni de %s MILD_ERR_SASLCRAMMD5_NO_PW_ATTR_185=\u00c9chec de l'authentification SASL CRAM-MD5 car l'entr\u00e9e utilisateur mapp\u00e9e ne contient pas de valeurs pour l'attribut %s MILD_ERR_SASLCRAMMD5_UNKNOWN_STORAGE_SCHEME_186=Impossible de traiter un mot de passe de l'entr\u00e9e utilisateur cible %s via SASL CRAM-MD5 car ce mot de passe poss\u00e8de un sch\u00e9ma de stockage de %s inconnu @@ -215,7 +359,9 @@ INFO_SASLCRAMMD5_UPDATED_USER_BASE_DN_191=L'attribut ds-cfg-user-base-dn de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. Le DN %s sera d\u00e9sormais utilis\u00e9 comme base de recherche d'entr\u00e9es utilisateur en fonction de leur nom d'utilisateur INFO_SASL_UNSUPPORTED_CALLBACK_192=Un rappel inattendu ou non pris en charge est fourni pour le serveur SASL lors de l'authentification %s\u00a0: %s MILD_ERR_SASL_NO_CREDENTIALS_193=La connexion client inclut les informations de statut %s, indiquant que le client effectue une liaison %s mais que la requ\u00eate de liaison n'inclut pas d'informations d'identification SEVERE_ERR_SASL_CANNOT_GET_SERVER_FQDN_194=An unexpected error occurred while attempting to determine the value of the ds-cfg-server-fqdn attribute in configuration entry %s: %s ###SEVERE_ERR_SASL_CANNOT_GET_SERVER_FQDN_194=An unexpected error occurred \ ### while attempting to determine the value of the ds-cfg-server-fqdn attribute \ ### in configuration entry %s: %s SEVERE_ERR_SASL_CONTEXT_CREATE_ERROR_195=Une erreur inattendue s'est produite lors de la cr\u00e9ation d'un contexte\u00a0%s : %s MILD_ERR_SASL_CANNOT_DECODE_USERNAME_AS_DN_196=Une erreur s'est produite lors du d\u00e9codage du nom d'utilisateur SASL %s "%s" car il semble contenir un DN dont le d\u00e9codage a \u00e9chou\u00e9\u00a0: %s MILD_ERR_SASL_USERNAME_IS_NULL_DN_197=Le nom d'utilisateur de la requ\u00eate de liaison SASL %s semble \u00eatre un DN vide. Cela n'est pas autoris\u00e9 @@ -230,20 +376,25 @@ MILD_ERR_SASL_CANNOT_MAP_AUTHZID_206=Une erreur s'est produite lors du mappage de l'ID d'autorisation %s \u00e0 une entr\u00e9e utilisateur\u00a0: %s MILD_ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDS_207=Une erreur s'est produite lors de la r\u00e9cup\u00e9ration d'au moins un mot de passe en texte clair pour l'utilisateur %s \u00e0 des fins d'authentification SASL %s\u00a0: %s MILD_ERR_SASL_NO_REVERSIBLE_PASSWORDS_208=Authentification SASL %s impossible pour l'utilisateur %s car aucun des mots de passe de l'entr\u00e9e utilisateur n'est stock\u00e9 sous forme r\u00e9versible SEVERE_ERR_SASL_PROTOCOL_ERROR_209=SASL %s protocol error: %s ###SEVERE_ERR_SASL_PROTOCOL_ERROR_209=SASL %s protocol error: %s MILD_ERR_SASL_AUTHZID_INSUFFICIENT_PRIVILEGES_210=L'utilisateur en cours d'authentification %s ne dispose pas des privil\u00e8ges suffisants pour assumer une identit\u00e9 d'autorisation diff\u00e9rente MILD_ERR_SASL_AUTHZID_INSUFFICIENT_ACCESS_211=L'utilisateur en cours d'authentification %s ne dispose pas des privil\u00e8ges suffisants pour assumer une identit\u00e9 d'autorisation diff\u00e9rente MILD_ERR_SASL_AUTHENTRY_NO_MAPPED_ENTRY_212=Impossible pour le serveur de trouver une entr\u00e9e correspondant \u00e0 l'ID d'authentification %s SEVERE_ERR_SASLGSSAPI_KDC_REALM_NOT_DEFINED_213=The server was unable to because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be defined or neither defined ###SEVERE_ERR_SASLGSSAPI_KDC_REALM_NOT_DEFINED_213=The server was unable to \ ### because both the ds-cfg-kdc-address and ds-cfg-realm attributes must be \ ### defined or neither defined MILD_ERR_SASL_CANNOT_MAP_AUTHENTRY_214=Une erreur s'est produite lors du mappage de l'ID d'autorisation %s \u00e0 une entr\u00e9e utilisateur\u00a0: %s SEVERE_ERR_SASLGSSAPI_CANNOT_CREATE_JAAS_CONFIG_215=An error occurred while attempting to write a temporary JAAS configuration file for use during GSSAPI processing: %s ###SEVERE_ERR_SASLGSSAPI_CANNOT_CREATE_JAAS_CONFIG_215=An error occurred while \ ### attempting to write a temporary JAAS configuration file for use during GSSAPI \ ### processing: %s SEVERE_ERR_SASLGSSAPI_CANNOT_CREATE_LOGIN_CONTEXT_216=Une erreur s'est produite lors de la cr\u00e9ation du contexte d'ouverture de session JAAS pour l'authentification GSSAPI\u00a0: %s MILD_ERR_SASLGSSAPI_NO_CLIENT_CONNECTION_217=Connexion client indisponible pour le traitement de la requ\u00eate de liaison GSSAPI INFO_GSSAPI_PRINCIPAL_NAME_218=M\u00e9canisme GSSAPI utilisant un nom principal\u00a0: %s INFO_GSSAPI_SERVER_FQDN_219=M\u00e9canisme GSSAPI SASL utilisant un nom de domaine complet de serveur\u00a0: %s INFO_DIGEST_MD5_REALM_220=M\u00e9canisme DIGEST-MD5 SASL utilisant un domaine\u00a0: %s INFO_DIGEST_MD5_SERVER_FQDN_221=M\u00e9canisme GSSAPI SASL utilisant un nom de domaine complet de serveur\u00a0: %s SEVERE_ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES_277=Vous ne disposez pas de privil\u00e8ges suffisants pour utiliser le contr\u00f4le d'autorisation proxy ###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=Nom ou OID de l'attribut dont la valeur doit correspondre exactement \u00e0 la cha\u00eene d'ID fournie \u00e0 ce mappeur d'identit\u00e9. Veuillez fournir au moins une valeur. Toutes les valeurs doivent faire r\u00e9f\u00e9rence au nom ou \u00e0 l'OID d'un type d'attribut d\u00e9fini dans le sch\u00e9ma Directory Server. Si plusieurs noms ou OID de type d'attribut sont fournis, au moins l'un de ces attributs doit contenir la valeur de la cha\u00eene d'ID dans une entr\u00e9e exactement MILD_ERR_EXACTMAP_NO_MATCH_ATTR_299=L'entr\u00e9e de configuration %s ne contient pas de valeur pour l'attribut ds-cfg-match-attribute, qui sp\u00e9cifie le ou les attributs \u00e0 utiliser pour mapper une cha\u00eene d'ID \u00e0 une entr\u00e9e utilisateur MILD_ERR_EXACTMAP_UNKNOWN_ATTR_300=L'entr\u00e9e de configuration %s contient la valeur %s pour l'attribut ds-cfg-match-attribute mais il ne s'agit pas d'un nom ou d'un OID valide pour les types d'attribut d\u00e9finis dans le sch\u00e9ma Directory Server @@ -255,19 +406,19 @@ MILD_ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_306=Cha\u00eene d'ID %s mapp\u00e9e \u00e0 plusieurs utilisateurs MILD_ERR_EXACTMAP_INEFFICIENT_SEARCH_307=Impossible de traiter efficacement la recherche interne bas\u00e9e sur la cha\u00eene d'ID %s\u00a0: %s. V\u00e9rifiez la configuration serveur pour vous assurer que tous les backends associ\u00e9s sont correctement configur\u00e9s pour ces types de recherches MILD_ERR_EXACTMAP_SEARCH_FAILED_308=Une erreur interne s'est produite lors de la r\u00e9solution de la cha\u00eene d'ID %s \u00e0 une entr\u00e9e utilisateur\u00a0: %s INFO_SASLCRAMMD5_DESCRIPTION_IDENTITY_MAPPER_DN_309=Le DN de l'entr\u00e9e de configuration contenant la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur CRAM-MD5 \u00e0 une entr\u00e9e utilisateur de Directory Server. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_SASLCRAMMD5_DESCRIPTION_IDENTITY_MAPPER_DN_309=Le DN de l'entr\u00e9e de configuration contenant la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur CRAM-MD5 \u00e0 une entr\u00e9e utilisateur de Directory Server. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_SASLCRAMMD5_NO_IDENTITY_MAPPER_ATTR_310=L'entr\u00e9e de configuration %s ne contient pas l'attribut ds-cfg-identity-mapper sp\u00e9cifiant le DN du mappeur d'identit\u00e9 \u00e0 utiliser conjointement au m\u00e9canisme CRAM-MD5 SASL. Cet argument est obligatoire MILD_ERR_SASLCRAMMD5_NO_SUCH_IDENTITY_MAPPER_311=Le mappeur d'identit\u00e9 %s sp\u00e9cifi\u00e9 dans l'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s ne r\u00e9f\u00e9rence pas de configuration de mappeur d'identit\u00e9 valide prise en charge par Directory Server MILD_ERR_SASLCRAMMD5_CANNOT_GET_IDENTITY_MAPPER_312=Une erreur s'est produite lors du traitement de la valeur de l'attribut ds-cfg-identity-mapper dans l'entr\u00e9e de configuration %s en vue de d\u00e9terminer le mappeur d'identit\u00e9 \u00e0 utiliser conjointement avec le m\u00e9canisme CRAM-MD5 SASL\u00a0: %s MILD_ERR_SASLCRAMMD5_CANNOT_MAP_USERNAME_313=Une erreur s'est produite lors du mappage du nom d'utilisateur %s \u00e0 une entr\u00e9e Directory Server\u00a0: %s INFO_SASLCRAMMD5_UPDATED_IDENTITY_MAPPER_314=L'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. Le mappeur d'identit\u00e9 d\u00e9fini dans l'entr\u00e9e de configuration %s sera d\u00e9sormais utilis\u00e9 pour mapper les noms d'utilisateur aux entr\u00e9es lors du traitement des requ\u00eates de liaison SASL CRAM-MD5 INFO_SASLDIGESTMD5_DESCRIPTION_IDENTITY_MAPPER_DN_315=Le DN de l'entr\u00e9e de configuration qui contient la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur DIGEST-MD5 \u00e0 une entr\u00e9e Directory Server. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_SASLDIGESTMD5_DESCRIPTION_IDENTITY_MAPPER_DN_315=Le DN de l'entr\u00e9e de configuration qui contient la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur DIGEST-MD5 \u00e0 une entr\u00e9e Directory Server. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_SASLDIGESTMD5_NO_IDENTITY_MAPPER_ATTR_316=L'entr\u00e9e de configuration %s ne contient pas l'attribut ds-cfg-identity-mapper qui sp\u00e9cifie le DN du mappeur d'identit\u00e9 \u00e0 utiliser conjointement au m\u00e9canisme DIGEST-MD5 SASL. Cet argument est obligatoire MILD_ERR_SASLDIGESTMD5_NO_SUCH_IDENTITY_MAPPER_317=Le mappeur d'identit\u00e9 %s sp\u00e9cifi\u00e9 dans l'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s ne r\u00e9f\u00e9rence pas de configuration de mappeur d'identit\u00e9 valide prise en charge par Directory Server MILD_ERR_SASLDIGESTMD5_CANNOT_GET_IDENTITY_MAPPER_318=Une erreur s'est produite lors du traitement de la valeur de l'attribut ds-cfg-identity-mapper dans l'entr\u00e9e de configuration %s en vue de d\u00e9terminer le mappeur d'identit\u00e9 \u00e0 utiliser conjointement avec le m\u00e9canisme DIGEST-MD5 SASL\u00a0: %s MILD_ERR_SASLDIGESTMD5_CANNOT_MAP_USERNAME_319=Une erreur s'est produite lors du mappage du nom d'utilisateur %s \u00e0 une entr\u00e9e Directory Server\u00a0: %s INFO_SASLDIGESTMD5_UPDATED_IDENTITY_MAPPER_320=L'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. Le mappeur d'identit\u00e9 d\u00e9fini dans l'entr\u00e9e de configuration %s sera d\u00e9sormais utilis\u00e9 pour mapper les noms d'utilisateur aux entr\u00e9es lors du traitement des requ\u00eates de liaison SASL DIGEST-MD5 INFO_SASLPLAIN_DESCRIPTION_IDENTITY_MAPPER_DN_321=DN de l'entr\u00e9e de configuration qui contient la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur fourni \u00e0 une entr\u00e9e Directory Server. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_SASLPLAIN_DESCRIPTION_IDENTITY_MAPPER_DN_321=DN de l'entr\u00e9e de configuration qui contient la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom d'utilisateur fourni \u00e0 une entr\u00e9e Directory Server. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_SASLPLAIN_NO_IDENTITY_MAPPER_ATTR_322=L'entr\u00e9e de configuration %s ne contient pas l'attribut ds-cfg-identity-mapper qui sp\u00e9cifie le DN du mappeur d'identit\u00e9 \u00e0 utiliser conjointement au m\u00e9canisme PLAIN SASL. Cet argument est obligatoire MILD_ERR_SASLPLAIN_NO_SUCH_IDENTITY_MAPPER_323=Le mappeur d'identit\u00e9 %s sp\u00e9cifi\u00e9 dans l'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s ne r\u00e9f\u00e9rence pas de configuration de mappeur d'identit\u00e9 valide prise en charge par Directory Server MILD_ERR_SASLPLAIN_CANNOT_GET_IDENTITY_MAPPER_324=Une erreur s'est produite lors du traitement de la valeur de l'attribut ds-cfg-identity-mapper dans l'entr\u00e9e de configuration %s en vue de d\u00e9terminer le mappeur d'identit\u00e9 \u00e0 utiliser conjointement avec le m\u00e9canisme PLAIN SASL\u00a0: %s @@ -277,25 +428,25 @@ MILD_ERR_EXTOP_CANCEL_CANNOT_DECODE_REQUEST_VALUE_328=Une erreur s'est produite lors du d\u00e9codage de la valeur de la demande d'annulation \u00e9tendue\u00a0: %s INFO_EXTOP_CANCEL_REASON_329=Le traitement de cette op\u00e9ration a pris fin suite \u00e0 la r\u00e9ception d'une demande d'annulation (ID de message %d) MILD_ERR_PWSCHEME_DOES_NOT_SUPPORT_AUTH_PASSWORD_330=Le sch\u00e9ma de stockage de mot de passe %s n'est pas compatible avec la syntaxe d'attribut de mot de passe d'authentification INFO_PWLENGTHVALIDATOR_DESCRIPTION_MIN_LENGTH_331=Nombre minimum de caract\u00e8res autoris\u00e9 pour un mot de passe. Z\u00e9ro indique qu'il n'existe pas de longueur minimale. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_PWLENGTHVALIDATOR_DESCRIPTION_MIN_LENGTH_331=Nombre minimum de caract\u00e8res autoris\u00e9 pour un mot de passe. Z\u00e9ro indique qu'il n'existe pas de longueur minimale. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_PWLENGTHVALIDATOR_CANNOT_DETERMINE_MIN_LENGTH_332=Une erreur s'est produite lors de la d\u00e9termination de la longueur de mot de passe minimale autoris\u00e9e \u00e0 partir de l'attribut ds-cfg-min-password-length\u00a0: %s INFO_PWLENGTHVALIDATOR_DESCRIPTION_MAX_LENGTH_333=Nombre maximum de caract\u00e8res autoris\u00e9 pour un mot de passe. Z\u00e9ro indique qu'il n'existe pas de longueur maximale. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_PWLENGTHVALIDATOR_DESCRIPTION_MAX_LENGTH_333=Nombre maximum de caract\u00e8res autoris\u00e9 pour un mot de passe. Z\u00e9ro indique qu'il n'existe pas de longueur maximale. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_PWLENGTHVALIDATOR_CANNOT_DETERMINE_MAX_LENGTH_334=Une erreur s'est produite lors de la d\u00e9termination de la longueur de mot de passe maximale autoris\u00e9e \u00e0 partir de l'attribut ds-cfg-max-password-length\u00a0: %s MILD_ERR_PWLENGTHVALIDATOR_MIN_GREATER_THAN_MAX_335=La longueur de mot de passe minimale configur\u00e9e (%d caract\u00e8res) est sup\u00e9rieure \u00e0 la longueur de mot de passe maximale configur\u00e9e, qui est de %d MILD_ERR_PWLENGTHVALIDATOR_TOO_SHORT_336=La longueur du mot de passe fourni est inf\u00e9rieure \u00e0 la longueur minimale requise de %d caract\u00e8res MILD_ERR_PWLENGTHVALIDATOR_TOO_LONG_337=La longueur du mot de passe fourni est sup\u00e9rieure \u00e0 la longueur maximale requise de %d caract\u00e8res INFO_PWLENGTHVALIDATOR_UPDATED_MIN_LENGTH_338=La longueur de mot de passe minimale a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %d INFO_PWLENGTHVALIDATOR_UPDATED_MAX_LENGTH_339=La longueur de mot de passe maximale a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %d INFO_RANDOMPWGEN_DESCRIPTION_CHARSET_340=Jeu(x) de caract\u00e8res devant \u00eatre utilis\u00e9(s) pour g\u00e9n\u00e9rer les mots de passe. Un nom (constitu\u00e9 uniquement de caract\u00e8res alphab\u00e9tiques ASCII) doit \u00eatre attribu\u00e9 \u00e0 chaque jeu de caract\u00e8res, imm\u00e9diatement suivi de deux-points et du jeu de caract\u00e8res \u00e0 inclure \u00e0 ce jeu. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_RANDOMPWGEN_DESCRIPTION_CHARSET_340=Jeu(x) de caract\u00e8res devant \u00eatre utilis\u00e9(s) pour g\u00e9n\u00e9rer les mots de passe. Un nom (constitu\u00e9 uniquement de caract\u00e8res alphab\u00e9tiques ASCII) doit \u00eatre attribu\u00e9 \u00e0 chaque jeu de caract\u00e8res, imm\u00e9diatement suivi de deux-points et du jeu de caract\u00e8res \u00e0 inclure \u00e0 ce jeu. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_RANDOMPWGEN_NO_CHARSETS_341=L'entr\u00e9e de configuration "%s" ne contient pas l'attribut ds-cfg-password-character-set qui sp\u00e9cifie les ensembles de caract\u00e8res \u00e0 utiliser lors de la g\u00e9n\u00e9ration du mot de passe. Cet argument est obligatoire MILD_ERR_RANDOMPWGEN_CHARSET_NAME_CONFLICT_342=L'entr\u00e9e de configuration "%s" contient plusieurs d\u00e9finitions pour le jeu de caract\u00e8res %s MILD_ERR_RANDOMPWGEN_CANNOT_DETERMINE_CHARSETS_343=Une erreur s'est produite lors du d\u00e9codage d'une ou plusieurs valeurs de l'attribut de configuration ds-cfg-password-character-set contenant le(s) jeu(x) de caract\u00e8res \u00e0 utiliser lors de la g\u00e9n\u00e9ration du mot de passe\u00a0: %s INFO_RANDOMPWGEN_DESCRIPTION_PWFORMAT_344=Format \u00e0 utiliser pour les mots de passe construits par ce g\u00e9n\u00e9rateur de mots de passe. La valeur doit \u00eatre une s\u00e9quence d'\u00e9l\u00e9ments d\u00e9limit\u00e9e par des virgules, dont chaque \u00e9l\u00e9ment est le nom du jeu de caract\u00e8res suivi d'une virgule et du nombre de caract\u00e8res choisi de mani\u00e8re al\u00e9atoire dans le jeu de caract\u00e8res. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_RANDOMPWGEN_DESCRIPTION_PWFORMAT_344=Format \u00e0 utiliser pour les mots de passe construits par ce g\u00e9n\u00e9rateur de mots de passe. La valeur doit \u00eatre une s\u00e9quence d'\u00e9l\u00e9ments d\u00e9limit\u00e9e par des virgules, dont chaque \u00e9l\u00e9ment est le nom du jeu de caract\u00e8res suivi d'une virgule et du nombre de caract\u00e8res choisi de mani\u00e8re al\u00e9atoire dans le jeu de caract\u00e8res. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_RANDOMPWGEN_NO_PWFORMAT_345=L'entr\u00e9e de configuration "%s" ne contient pas l'attribut ds-cfg-password-format qui sp\u00e9cifie le format \u00e0 utiliser pour le mot de passe g\u00e9n\u00e9r\u00e9. Cet argument est obligatoire MILD_ERR_RANDOMPWGEN_UNKNOWN_CHARSET_346=La cha\u00eene de format de mot de passe "%s" r\u00e9f\u00e9rence un jeu de caract\u00e8re non d\u00e9fini "%s" MILD_ERR_RANDOMPWGEN_INVALID_PWFORMAT_347=La cha\u00eene de format de mot de passe "%s" contient une syntaxe non valide. La valeur doit \u00eatre une s\u00e9quence d'\u00e9l\u00e9ments d\u00e9limit\u00e9e par des virgules, dont chaque \u00e9l\u00e9ment est le nom du jeu de caract\u00e8res suivi d'une virgule et du nombre de caract\u00e8res choisi de mani\u00e8re al\u00e9atoire dans ce jeu de caract\u00e8res. MILD_ERR_RANDOMPWGEN_CANNOT_DETERMINE_PWFORMAT_348=Une erreur s'est produite lors du d\u00e9codage de la valeur de l'attribut de configuration ds-cfg-password-format sp\u00e9cifiant le format des mots de passe g\u00e9n\u00e9r\u00e9s : %s INFO_SASLGSSAPI_DESCRIPTION_IDENTITY_MAPPER_DN_349=Le DN de l'entr\u00e9e de configuration contenant la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom GSSAPI principal \u00e0 une entr\u00e9e d'utilisateur Directory Server. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_SASLGSSAPI_DESCRIPTION_IDENTITY_MAPPER_DN_349=Le DN de l'entr\u00e9e de configuration contenant la configuration du mappeur d'identit\u00e9 \u00e0 utiliser pour mapper le nom GSSAPI principal \u00e0 une entr\u00e9e d'utilisateur Directory Server. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_SASLGSSAPI_NO_IDENTITY_MAPPER_ATTR_350=L'entr\u00e9e de configuration %s ne contient pas l'attribut ds-cfg-identity-mapper sp\u00e9cifiant le DN du mappeur d'identit\u00e9 \u00e0 utiliser conjointement au m\u00e9canisme GSSAPI SASL. Cet argument est obligatoire MILD_ERR_SASLGSSAPI_NO_SUCH_IDENTITY_MAPPER_351=Le mappeur d'identit\u00e9 %s sp\u00e9cifi\u00e9 dans l'attribut ds-cfg-identity-mapper de l'entr\u00e9e de configuration %s ne r\u00e9f\u00e9rence pas de configuration de mappeur d'identit\u00e9 valide prise en charge par Directory Server MILD_ERR_SASLGSSAPI_CANNOT_GET_IDENTITY_MAPPER_352=Une erreur s'est produite lors du traitement de la valeur de l'attribut ds-cfg-identity-mapper dans l'entr\u00e9e de configuration %s en vue de d\u00e9terminer le mappeur d'identit\u00e9 \u00e0 utiliser conjointement avec le m\u00e9canisme GSSAPI SASL\u00a0: %s @@ -320,11 +471,6 @@ MILD_ERR_ERRORLOG_ACCTNOTHANDLER_INVALID_TYPE_373=L'entr\u00e9e de configuration %s contient un type de notification de statut de compte %s non reconnu MILD_ERR_ERRORLOG_ACCTNOTHANDLER_CANNOT_GET_NOTIFICATION_TYPES_374=Une erreur s'est produite lors de la d\u00e9termination des types de notification statut de compte \u00e0 partir de l'entr\u00e9e de configuration %s\u00a0: %s NOTICE_ERRORLOG_ACCTNOTHANDLER_NOTIFICATION_375=Account-Status-Notification type='%s' userdn='%s' id=%d msg='%s' MILD_ERR_SASLCRAMMD5_CANNOT_GET_REVERSIBLE_PASSWORDS_377=Une erreur s'est produite lors de la r\u00e9cup\u00e9ration d'au moins un mot de passe en texte clair pour l'utilisateur %s \u00e0 des fins d'authentification SASL CRAM-MD5\u00a0: %s MILD_ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITY_378=Une erreur s'est produite lors de la v\u00e9rification du mot de passe pour l'utilisateur %s lors de l'authentification SASL PLAIN\u00a0: %s MILD_ERR_STARTTLS_ERROR_SENDING_CLEAR_RESPONSE_379=Une erreur inattendue s'est produite lors de l'envoi d'une r\u00e9ponse en texte clair au client apr\u00e8s le d\u00e9marrage de la n\u00e9gociation TLS\u00a0: %s @@ -341,77 +487,113 @@ MILD_ERR_STATICGROUP_ADD_MEMBER_UPDATE_FAILED_390=Impossible d'ajouter l'utilisateur %s comme nouveau membre du groupe statique %s car une erreur s'est produite lors de la modification interne destin\u00e9e \u00e0 mettre \u00e0 jour le groupe\u00a0: %s MILD_ERR_STATICGROUP_REMOVE_MEMBER_UPDATE_FAILED_391=Impossible de supprimer l'utilisateur %s comme membre du groupe statique %s car une erreur s'est produite lors de la modification interne destin\u00e9e \u00e0 mettre \u00e0 jour le groupe\u00a0: %s MILD_ERR_EXTOP_PASSMOD_INSUFFICIENT_PRIVILEGES_392=Vous ne disposez pas des privil\u00e8ges suffisants pour ex\u00e9cuter des op\u00e9rations de r\u00e9initialisation de mot de passe MILD_ERR_SASLDIGESTMD5_EMPTY_AUTHZID_393=L'ID d'autorisation fournie est vide, ce qui n'est pas autoris\u00e9 dans le cadre de l'authentification DIGEST-MD5 MILD_ERR_SASLDIGESTMD5_AUTHZID_INVALID_DN_394=L'ID d'autorisation fournie %s contient un DN non valide\u00a0: %s MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_SUCH_ENTRY_396=L'entr\u00e9e %s sp\u00e9cifi\u00e9e comme identit\u00e9 d'autorisation n'existe pas MILD_ERR_SASLDIGESTMD5_AUTHZID_CANNOT_GET_ENTRY_397=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e %s sp\u00e9cifi\u00e9e comme identit\u00e9 d'autorisation\u00a0: %s MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_MAPPED_ENTRY_398=Impossible pour le serveur de trouver une entr\u00e9e correspondant \u00e0 l'ID d'autorisation %s MILD_ERR_SASLDIGESTMD5_CANNOT_MAP_AUTHZID_399=Une erreur s'est produite lors du mappage de l'ID d'autorisation %s \u00e0 une entr\u00e9e utilisateur\u00a0: %s MILD_ERR_SASLPLAIN_AUTHZID_INVALID_DN_400=L'ID d'autorisation fournie %s contient un DN non valide\u00a0: %s MILD_ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGES_401=L'utilisateur en cours d'authentification %s ne poss\u00e8de pas les privil\u00e8ges suffisants pour sp\u00e9cifier une ID d'autorisation de remplacement MILD_ERR_SASLPLAIN_AUTHZID_NO_SUCH_ENTRY_402=L'entr\u00e9e correspondant au DN d'autorisation %s n'existe pas dans Directory Server MILD_ERR_SASLPLAIN_AUTHZID_CANNOT_GET_ENTRY_403=Une erreur s'est produite lors de la r\u00e9cup\u00e9ration de l'entr\u00e9e %s sp\u00e9cifi\u00e9e comme ID d'autorisation\u00a0: %s MILD_ERR_SASLPLAIN_AUTHZID_NO_MAPPED_ENTRY_404=Impossible de trouver une entr\u00e9e correspondant \u00e0 l'ID d'autorisation %s sur le serveur MILD_ERR_SASLPLAIN_AUTHZID_CANNOT_MAP_AUTHZID_405=Une erreur s'est produite lors du mappage de l'ID d'autorisation %s \u00e0 une entr\u00e9e utilisateur\u00a0: %s INFO_SASLEXTERNAL_DESCRIPTION_CERT_MAPPER_DN_406=Le DN de l'entr\u00e9e de configuration d\u00e9finissant le mappeur de certificat \u00e0 utiliser lors du mappage d'un certificat \u00e0 une entr\u00e9e utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_SASLEXTERNAL_DESCRIPTION_CERT_MAPPER_DN_406=Le DN de l'entr\u00e9e de configuration d\u00e9finissant le mappeur de certificat \u00e0 utiliser lors du mappage d'un certificat \u00e0 une entr\u00e9e utilisateur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_SASLEXTERNAL_NO_CERTIFICATE_MAPPER_DN_407=L'entr\u00e9e de configuration %s ne contient pas l'attribut ds-cfg-certificate-mapper obligatoire pour sp\u00e9cifier le mappeur de certificat \u00e0 utiliser pour mapper les certificats aux entr\u00e9es utilisateur MILD_ERR_SASLEXTERNAL_INVALID_CERTIFICATE_MAPPER_DN_408=L'entr\u00e9e de configuration %s contient un DN de mappeur de certificat de %s, mais ce type de mappeur n'est pas compatible avec Directory Server MILD_ERR_SASLEXTERNAL_CANNOT_GET_CERT_MAPPER_DN_409=Une erreur s'est produite lors de la r\u00e9cup\u00e9ration du DN du mappeur de certificat \u00e0 partir de l'entr\u00e9e de configuration %s\u00a0: %s INFO_SASLEXTERNAL_UPDATED_CERT_MAPPER_DN_410=L'attribut ds-cfg-certificate-mapper de l'entr\u00e9e de configuration %s a \u00e9t\u00e9 mis \u00e0 jour. Le mappeur de certificat %s sera d\u00e9sormais utilis\u00e9 pour mapper les certificats aux entr\u00e9es utilisateur INFO_SDTUACM_DESCRIPTION_SUBJECT_ATTR_411=Nom du type d'attribut des entr\u00e9es utilisateur contenant les sujets des certificats d\u00e9tenus par cet utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront effectu\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car aucun certificat de pair n'est disponible SEVERE_ERR_SDTUACM_PEER_CERT_NOT_X509_418=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car le certificat de pair n'est pas un certificat X.509 (le format de certificat de pair est %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=Nom du type d'attribut des entr\u00e9es utilisateur qui d\u00e9finit le mappage entre les attributs des sujets du certificat et ceux des entr\u00e9es utilisateur. Le format des valeurs doit \u00eatre 'certattr:userattr'. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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' SEVERE_ERR_SATUACM_DUPLICATE_CERT_ATTR_423=Configuration entry %s contains multiple mappings for certificate attribute %s SEVERE_ERR_SATUACM_NO_SUCH_ATTR_424=Mapping %s in configuration entry %s 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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront effectu\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car aucun certificat de pair n'est disponible SEVERE_ERR_SATUACM_PEER_CERT_NOT_X509_430=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car le certificat de pair n'est pas un certificat X.509 (le format de certificat de pair est %s) SEVERE_ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DN_431=Unable to decode peer certificate subject %s as a DN: %s SEVERE_ERR_SATUACM_NO_MAPPABLE_ATTRIBUTES_432=Peer certificate subject %s 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=Nom du type d'attribut des entr\u00e9es utilisateur contenant les empreintes des certificats d\u00e9tenus par cet utilisateur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=Nom de l'algorithme Digest utilis\u00e9 pour les empreintes de certificat. La valeur doit \u00eatre 'MD5' ou 'SHA1'. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront effectu\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte 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=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car aucun certificat de pair n'est disponible SEVERE_ERR_FCM_PEER_CERT_NOT_X509_444=Impossible de mapper la cha\u00eene de certificat fournie \u00e0 une entr\u00e9e utilisateur car le certificat de pair n'est pas un certificat X.509 (le format de certificat de pair est %s) SEVERE_ERR_FCM_CANNOT_CALCULATE_FINGERPRINT_445=An error occurred while attempting to calculate the fingerprint for the peer certificate with subject %s: %s SEVERE_ERR_FCM_MULTIPLE_MATCHING_ENTRIES_446=The certificate with fingerprint %s could not be mapped to exactly one user. It maps to both %s and %s INFO_SDTUACM_DESCRIPTION_SUBJECT_ATTR_411=Nom du type d'attribut des entr\u00e9es utilisateur contenant les sujets des certificats d\u00e9tenus par cet utilisateur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront effectu\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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 chain to a user because the peer certificate was not an X.509 \ ### 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=Nom du type d'attribut des entr\u00e9es utilisateur qui d\u00e9finit le mappage entre les attributs des sujets du certificat et ceux des entr\u00e9es utilisateur. Le format des valeurs doit \u00eatre 'certattr:userattr'. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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' ###SEVERE_ERR_SATUACM_DUPLICATE_CERT_ATTR_423=Configuration entry %s contains \ ### multiple mappings for certificate attribute %s ###SEVERE_ERR_SATUACM_NO_SUCH_ATTR_424=Mapping %s in configuration entry %s \ ### 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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront effectu\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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 \ ### certificate chain to a user because the peer certificate was not an X.509 \ ### certificate (peer certificate format was %s) ###SEVERE_ERR_SATUACM_CANNOT_DECODE_SUBJECT_AS_DN_431=Unable to decode peer \ ### certificate subject %s as a DN: %s ###SEVERE_ERR_SATUACM_NO_MAPPABLE_ATTRIBUTES_432=Peer certificate subject %s \ ### 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=Nom du type d'attribut des entr\u00e9es utilisateur contenant les empreintes des certificats d\u00e9tenus par cet utilisateur. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=Nom de l'algorithme Digest utilis\u00e9 pour les empreintes de certificat. La valeur doit \u00eatre 'MD5' ou 'SHA1'. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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=DN de base sous lesquels les recherches d'entr\u00e9es utilisateur correspondantes seront ex\u00e9cut\u00e9es. Si aucun DN de base n'est fourni, le serveur effectue une recherche sous tous les contextes de nommage publics. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte ###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 \ ### chain to a user because the peer certificate was not an X.509 certificate \ ### (peer certificate format was %s) ###SEVERE_ERR_FCM_CANNOT_CALCULATE_FINGERPRINT_445=An error occurred while \ ### attempting to calculate the fingerprint for the peer certificate with subject \ ### %s: %s ###SEVERE_ERR_FCM_MULTIPLE_MATCHING_ENTRIES_446=The certificate with fingerprint \ ### %s could not be mapped to exactly one user. It maps to both %s and %s MILD_ERR_DYNAMICGROUP_CANNOT_DECODE_MEMBERURL_447=Impossible de d\u00e9coder la valeur "%s" de l'entr\u00e9e "%s" comme URL LDAP\u00a0: %s MILD_ERR_DYNAMICGROUP_NESTING_NOT_SUPPORTED_448=Les groupes dynamiques ne prennent pas en charge les groupes imbriqu\u00e9s MILD_ERR_DYNAMICGROUP_ALTERING_MEMBERS_NOT_SUPPORTED_449=Les groupes dynamiques ne prennent pas en charge la modification explicite de leur adh\u00e9sion MILD_WARN_DYNAMICGROUP_NONEXISTENT_BASE_DN_450=Le DN de base %s sp\u00e9cifi\u00e9 dans le groupe dynamique %s n'existe pas dans le serveur SEVERE_ERR_DYNAMICGROUP_INTERNAL_SEARCH_FAILED_451=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 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=Diff\u00e9rence minimale autoris\u00e9e pour un mot de passe. La valeur z\u00e9ro indique qu'il n'existe pas de diff\u00e9rence minimale. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte ###SEVERE_ERR_DYNAMICGROUP_INTERNAL_SEARCH_FAILED_451=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 ###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=Diff\u00e9rence minimale autoris\u00e9e pour un mot de passe. La valeur z\u00e9ro indique qu'il n'existe pas de diff\u00e9rence minimale. Les modifications apport\u00e9es \u00e0 cette configuration seront imm\u00e9diatement prises en compte MILD_ERR_PWDIFFERENCEVALIDATOR_CANNOT_DETERMINE_MIN_DIFFERENCE_454=Une erreur s'est produite lors de la d\u00e9termination de la diff\u00e9rence de mot de passe minimale autoris\u00e9e \u00e0 partir de l'attribut ds-cfg-min-password-difference\u00a0: %s INFO_PWDIFFERENCEVALIDATOR_UPDATED_MIN_DIFFERENCE_455=La diff\u00e9rence de mot de passe minimale a \u00e9t\u00e9 mise \u00e0 jour et est maintenant %d MILD_ERR_PWDIFFERENCEVALIDATOR_TOO_SMALL_456=La diff\u00e9rence du mot de passe fourni est inf\u00e9rieure \u00e0 la diff\u00e9rence minimale autoris\u00e9e de %d caract\u00e8res @@ -437,53 +619,127 @@ MILD_ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUAL_476=Le groupe statique virtuel %s r\u00e9f\u00e9rence le groupe cible %s qui est \u00e9galement un groupe statique virtuel. Un groupe statique virtuel ne peut pas en r\u00e9f\u00e9rencer un autre comme groupe cible NOTICE_FSCACHE_RESTORE_484=D\u00e9but de la restauration de l'\u00e9tat de cache d'entr\u00e9e persistant, cette op\u00e9ration peut prendre un certain temps NOTICE_FSCACHE_SAVE_485=D\u00e9finition de la persistance de l'\u00e9tat du cache d'entr\u00e9e, cette op\u00e9ration peut prendre un certain temps FATAL_ERR_FSCACHE_CANNOT_INITIALIZE_486=A fatal error occurred while trying to initialize file system entry cache: %s SEVERE_ERR_FSCACHE_CANNOT_LOAD_PERSISTENT_DATA_487=An error occurred while trying to load persistent cache. Persistent cache will be flushed now SEVERE_ERR_FSCACHE_CANNOT_STORE_PERSISTENT_DATA_488=An error occurred while trying to store persistent cache. Persistent cache will be flushed now SEVERE_ERR_FSCACHE_CANNOT_STORE_ENTRY_489=Unable to store new cache entry in the file system entry cache SEVERE_ERR_FSCACHE_CANNOT_RETRIEVE_ENTRY_490=Unable to retrieve an existing cache entry from the file system entry cache SEVERE_ERR_FSCACHE_CANNOT_SET_JE_MEMORY_PCT_491=Internal error occurred while trying to set the entry cache backend internal cache size as percentage. The previous or default value will be used instead SEVERE_ERR_FSCACHE_CANNOT_SET_JE_MEMORY_SIZE_492=Internal error occurred while trying to set the entry cache backend internal cache size in bytes. The previous or default value will be used instead SEVERE_ERR_FSCACHE_CANNOT_SET_JE_PROPERTIES_493=Internal error occurred while trying to set the entry cache backend Berkeley DB JE properties: %s FATAL_ERR_FSCACHE_HOMELESS_494=A fatal error occurred while trying to setup file system entry cache home. No suitable path can be found to host the cache home SEVERE_WARN_FSCACHE_SET_PERMISSIONS_FAILED_495=Unable to set file permissions for the file system entry cache backend database directory %s SEVERE_WARN_FSCACHE_OFFLINE_STATE_FAIL_496=%s backend current offline state does not match persistent cache last recorded offline state. All cached data for this backend is now discarded ###FATAL_ERR_FSCACHE_CANNOT_INITIALIZE_486=A fatal error occurred while trying \ ### to initialize file system entry cache: %s ###SEVERE_ERR_FSCACHE_CANNOT_LOAD_PERSISTENT_DATA_487=An error occurred while \ ### trying to load persistent cache. Persistent cache will be flushed now ###SEVERE_ERR_FSCACHE_CANNOT_STORE_PERSISTENT_DATA_488=An error occurred while \ ### trying to store persistent cache. Persistent cache will be flushed now ###SEVERE_ERR_FSCACHE_CANNOT_STORE_ENTRY_489=Unable to store new cache entry in \ ### the file system entry cache ###SEVERE_ERR_FSCACHE_CANNOT_RETRIEVE_ENTRY_490=Unable to retrieve an existing \ ### cache entry from the file system entry cache ###SEVERE_ERR_FSCACHE_CANNOT_SET_JE_MEMORY_PCT_491=Internal error occurred while \ ### trying to set the entry cache backend internal cache size as percentage. The \ ### previous or default value will be used instead ###SEVERE_ERR_FSCACHE_CANNOT_SET_JE_MEMORY_SIZE_492=Internal error occurred \ ### while trying to set the entry cache backend internal cache size in bytes. The \ ### previous or default value will be used instead ###SEVERE_ERR_FSCACHE_CANNOT_SET_JE_PROPERTIES_493=Internal error occurred \ ### while trying to set the entry cache backend Berkeley DB JE properties: %s ###FATAL_ERR_FSCACHE_HOMELESS_494=A fatal error occurred while trying to setup \ ### file system entry cache home. No suitable path can be found to host the cache \ ### home ###SEVERE_WARN_FSCACHE_SET_PERMISSIONS_FAILED_495=Unable to set file permissions \ ### for the file system entry cache backend database directory %s ###SEVERE_WARN_FSCACHE_OFFLINE_STATE_FAIL_496=%s backend current offline state \ ### does not match persistent cache last recorded offline state. All cached data \ ### for this backend is now discarded NOTICE_FSCACHE_RESTORE_REPORT_497=Entr\u00e9es de cache persistantes %d restaur\u00e9es dans le cache d'entr\u00e9es NOTICE_FSCACHE_SAVE_REPORT_498=Entr\u00e9es de cache %d d\u00e9finies comme persistantes NOTICE_FSCACHE_INDEX_NOT_FOUND_499=\u00c9tat d'entr\u00e9e de cache persistant pr\u00e9c\u00e9dent introuvable. D\u00e9marrage avec un cache vide SEVERE_ERR_FSCACHE_INDEX_IMPAIRED_500=The persistent cache index is inconsistent or damaged. Persistent cache will be flushed now ###SEVERE_ERR_FSCACHE_INDEX_IMPAIRED_500=The persistent cache index is \ ### inconsistent or damaged. Persistent cache will be flushed now MILD_ERR_ENTRYUUID_VATTR_NOT_SEARCHABLE_501=L'attribut %s ne peut pas faire l'objet d'une recherche et ne doit pas \u00eatre inclus dans des filtres de recherche non index\u00e9s SEVERE_ERR_PWPSTATE_EXTOP_NO_PRIVILEGE_502=You do not have sufficient privileges to use the password policy state extended operation SEVERE_ERR_PWPSTATE_EXTOP_NO_REQUEST_VALUE_503=The provided password policy state extended request did not include a request value SEVERE_ERR_PWPSTATE_EXTOP_DECODE_FAILURE_504=An unexpected error occurred while attempting to decode password policy state extended request value: %s SEVERE_ERR_PWPSTATE_EXTOP_MULTIPLE_ENTRIES_505=Multiple entries were found with DN %s SEVERE_ERR_PWPSTATE_EXTOP_INVALID_OP_ENCODING_506=An unexpected error occurred while attempting to decode an operation from the password policy state extended request: %s SEVERE_ERR_PWPSTATE_EXTOP_NO_DISABLED_VALUE_507=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_COUNT_508=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_509=The value provided for the password policy state operation intended to set the disabled state for the user was invalid. La valeur doit \u00eatre 'true' ou 'false' SEVERE_ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_COUNT_510=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_511=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_COUNT_512=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_513=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_COUNT_514=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_515=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_ADD_FAILURE_TIME_COUNT_516=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIME_517=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_COUNT_518=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_519=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 SEVERE_ERR_PWPSTATE_EXTOP_NO_RESET_STATE_VALUE_520=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_COUNT_521=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_522=The value provided for the password policy state operation intended to set the reset state for the user was invalid. La valeur doit \u00eatre 'true' ou 'false' SEVERE_ERR_PWPSTATE_EXTOP_BAD_ADD_GRACE_LOGIN_TIME_COUNT_523=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIME_524=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_COUNT_525=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 SEVERE_ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_526=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 SEVERE_ERR_PWPSTATE_EXTOP_UNKNOWN_OP_TYPE_527=The password policy state extended request included an operation with an invalid or unsupported operation type of %s ###SEVERE_ERR_PWPSTATE_EXTOP_NO_PRIVILEGE_502=You do not have sufficient \ ### privileges to use the password policy state extended operation ###SEVERE_ERR_PWPSTATE_EXTOP_NO_REQUEST_VALUE_503=The provided password policy \ ### state extended request did not include a request value ###SEVERE_ERR_PWPSTATE_EXTOP_DECODE_FAILURE_504=An unexpected error occurred \ ### while attempting to decode password policy state extended request value: %s ###SEVERE_ERR_PWPSTATE_EXTOP_MULTIPLE_ENTRIES_505=Multiple entries were found \ ### with DN %s ###SEVERE_ERR_PWPSTATE_EXTOP_INVALID_OP_ENCODING_506=An unexpected error \ ### occurred while attempting to decode an operation from the password policy \ ### state extended request: %s ###SEVERE_ERR_PWPSTATE_EXTOP_NO_DISABLED_VALUE_507=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_COUNT_508=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_DISABLED_VALUE_509=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' ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_COUNT_510=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_ACCT_EXP_VALUE_511=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_COUNT_512=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWCHANGETIME_VALUE_513=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_COUNT_514=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_PWWARNEDTIME_VALUE_515=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_ADD_FAILURE_TIME_COUNT_516=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_AUTH_FAILURE_TIME_517=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_COUNT_518=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_LAST_LOGIN_TIME_519=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 ###SEVERE_ERR_PWPSTATE_EXTOP_NO_RESET_STATE_VALUE_520=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_COUNT_521=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_RESET_STATE_VALUE_522=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' ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_ADD_GRACE_LOGIN_TIME_COUNT_523=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_GRACE_LOGIN_TIME_524=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_COUNT_525=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 ###SEVERE_ERR_PWPSTATE_EXTOP_BAD_REQUIRED_CHANGE_TIME_526=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 ###SEVERE_ERR_PWPSTATE_EXTOP_UNKNOWN_OP_TYPE_527=The password policy state \ ### extended request included an operation with an invalid or unsupported \ ### operation type of %s MILD_WARN_EXTOP_PASSMOD_CANNOT_UPDATE_PWP_STATE_528=Une erreur s'est produite lors de la mise \u00e0 jour des informations d'\u00e9tat de la strat\u00e9gie de mot de passe pour l'utilisateur %s dans le cadre d'une op\u00e9ration \u00e9tendue de modification de mot de passe (code de r\u00e9sultat='%s', message d'erreur='%s') MILD_ERR_SASLDIGESTMD5_INVALID_DIGEST_URI_529=Les informations d'identification DIGEST-MD5 fournies par le client demandent une URI Digest non valide de %s. L'URI Digest attendue est %s MILD_ERR_EXTOP_PASSMOD_PW_IN_HISTORY_530=Le nouveau mot de passe fourni se trouve d\u00e9j\u00e0 dans l'historique de mot de passe MILD_ERR_SMTPALERTHANDLER_NO_SMTP_SERVERS_531=Directory Server n'est pas configur\u00e9 avec des serveurs SMTP. Impossible d'utiliser le gestionnaire d'alertes SMTP sauf si la configuration Directory Server comporte des informations sur au moins un serveur SMTP SEVERE_WARN_SMTPALERTHANDLER_ERROR_SENDING_MESSAGE_532=An error occurred when trying to send an e-mail message for administrative alert with type %s and message %s: %s ###SEVERE_WARN_SMTPALERTHANDLER_ERROR_SENDING_MESSAGE_532=An error occurred when \ ### trying to send an e-mail message for administrative alert with type %s and \ ### message %s: %s MILD_ERR_REGEXMAP_INVALID_MATCH_PATTERN_533=Impossible d'analyser le mod\u00e8le de correspondance "%s" fourni en tant qu'expression r\u00e9guli\u00e8re\u00a0: %s MILD_ERR_REGEXMAP_UNKNOWN_ATTR_534=L'entr\u00e9e de configuration %s contient la valeur %s pour l'attribut ds-cfg-match-attribute mais il ne s'agit pas d'un nom ou d'un OID valide pour les types d'attribut d\u00e9finis dans le sch\u00e9ma Directory Server MILD_ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_535=Cha\u00eene d'ID %s trait\u00e9e mapp\u00e9e \u00e0 plusieurs utilisateurs @@ -509,21 +765,36 @@ MILD_ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKEN_555=Un jeton non reconnu %s a \u00e9t\u00e9 trouv\u00e9 dans la colonne %d de la ligne %d MILD_ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSE_556=Une erreur s'est produite lors de l'analyse du fichier de mod\u00e8le de message '%s' r\u00e9f\u00e9renc\u00e9 dans l'entr\u00e9e de configuration '%s'\u00a0: %s INFO_SMTP_ASNH_DEFAULT_SUBJECT_557=Notification d'\u00e9tat de compte du r\u00e9pertoire SEVERE_ERR_SMTP_ASNH_CANNOT_SEND_MESSAGE_558=An error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %s SEVERE_ERR_PWSCHEME_CANNOT_ENCRYPT_559=An error occurred while trying to encrypt a value using password storage scheme %s: %s SEVERE_ERR_PWSCHEME_CANNOT_DECRYPT_560=An error occurred while trying to decrypt a value using password storage scheme %s: %s ###SEVERE_ERR_SMTP_ASNH_CANNOT_SEND_MESSAGE_558=An error occurred while \ ### attempting to send an account status notification message for notification \ ### type %s for user entry %s: %s ###SEVERE_ERR_PWSCHEME_CANNOT_ENCRYPT_559=An error occurred while trying to \ ### encrypt a value using password storage scheme %s: %s ###SEVERE_ERR_PWSCHEME_CANNOT_DECRYPT_560=An error occurred while trying to \ ### decrypt a value using password storage scheme %s: %s MILD_ERR_GET_SYMMETRIC_KEY_NO_VALUE_561=Impossible de d\u00e9coder l'op\u00e9ration de cl\u00e9 sym\u00e9trique \u00e9tendue fournie car elle ne poss\u00e8de pas de valeur MILD_ERR_GET_SYMMETRIC_KEY_INVALID_TYPE_562=Impossible de d\u00e9coder l'op\u00e9ration de cl\u00e9 sym\u00e9trique \u00e9tendue fournie car la s\u00e9quence de valeur poss\u00e8de un \u00e9l\u00e9ment avec un type invalide de %s MILD_ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTION_563=Impossible de d\u00e9coder la requ\u00eate de cl\u00e9 sym\u00e9trique \u00e9tendue fournie \u00a0:%s MILD_ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTION_564=Une erreur inattendue s'est produite lors du d\u00e9codage de la s\u00e9quence de requ\u00eate \u00e9tendue de cl\u00e9 sym\u00e9trique\u00a0: %s SEVERE_ERR_EXACTMAP_ATTR_UNINDEXED_565=The exact match 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_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 ###SEVERE_ERR_EXACTMAP_ATTR_UNINDEXED_565=The exact match 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_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 INFO_LOG_EXTENSION_INFORMATION_571=Charg\u00e9 l'extension \u00e0 partir du fichier '%s' (version %s, r\u00e9vision %s) SEVERE_ERR_SASL_CREATE_SASL_SERVER_FAILED_572=\u00c9chec de cr\u00e9ation de serveurSASL pour le m\u00e9canisme SASL %s utilisant un FQDN de serveur de %s SEVERE_ERR_SASL_GSSAPI_KEYTAB_INVALID_573=GSSAPI SASL mechanism handler initalization failed because the keytab file %s does not exist ###SEVERE_ERR_SASL_GSSAPI_KEYTAB_INVALID_573=GSSAPI SASL mechanism handler initalization \ ###failed because the keytab file %s does not exist INFO_GSSAPI_STARTED_574=Initialisation du gestionnaire de m\u00e9canisme SASL GSSAPI INFO_GSSAPI_STOPPED_575=Le gestionnaire de m\u00e9canisme SASL GSSAPI s'est arr\u00eat\u00e9
