mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git
opendj-sdk/opends/src/messages/messages/protocol_fr.properties
@@ -21,14 +21,10 @@ # CDDL HEADER END # # Copyright 2006-2009 Sun Microsystems, Inc. # # Global directives # global.category=PROTOCOL global.category=PROTOCOLE # # Format string definitions # @@ -189,25 +185,51 @@ MILD_ERR_LDAP_CLIENT_DECODE_INVALID_MULTIBYTE_LENGTH_169=Le client a envoy\u00e9 une demande \u00e0 Directory Server avec un \u00e9l\u00e9ment ASN.1 qui utilise plusieurs octets pour exprimer la longueur de la valeur. La demande indiquait que %d octets \u00e9taient requis pour exprimer la longueur, mais cela exc\u00e8de la limite maximale autoris\u00e9e de quatre octets MILD_ERR_LDAP_CLIENT_DECODE_ASN1_FAILED_170=Le client a envoy\u00e9 une demande \u00e0 Directory Server qui n'a pas pu \u00eatre correctement d\u00e9cod\u00e9e en tant qu'\u00e9l\u00e9ment ASN.1\u00a0: %s MILD_ERR_LDAP_CLIENT_DECODE_LDAP_MESSAGE_FAILED_171=Le client a envoy\u00e9 une demande \u00e0 Directory Server qui n'a pas pu \u00eatre correctement d\u00e9cod\u00e9e en tant que message LDAP\u00a0: %s SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has occurred within the Directory Server to cause it to lose track of where it is in decoding requests on this client connection. It had an invalid decode state of %d, and this connection must be terminated ###SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has \ ### occurred within the Directory Server to cause it to lose track of where it is \ ### in decoding requests on this client connection. It had an invalid decode \ ### state of %d, and this connection must be terminated MILD_ERR_LDAP_CLIENT_DECODE_INVALID_REQUEST_TYPE_173=Le client a envoy\u00e9 un message LDAP \u00e0 Directory Server qui n'\u00e9tait pas valide pour une demande cliente\u00a0: %s MILD_ERR_LDAP_CLIENT_CANNOT_CONVERT_MESSAGE_TO_OPERATION_174=Directory Server n'a pas pu convertir le message LDAP lu \u00e0 partir du client (%s) en op\u00e9ration interne pour le traitement\u00a0: %s MILD_ERR_LDAP_ABANDON_INVALID_MESSAGE_TYPE_175=Impossible de convertir le message LDAP fourni (%s) en op\u00e9ration d'abandon\u00a0: %s MILD_ERR_LDAP_UNBIND_INVALID_MESSAGE_TYPE_176=Impossible de convertir le message LDAP fourni (%s) en op\u00e9ration de dissociation\u00a0: %s FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection handler defined in configuration entry %s was unable to open a selector to allow it to multiplex the associated accept sockets: %s. This connection handler will be disabled SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection handler defined in configuration entry %s was unable to create a server socket channel to accept connections on %s:%d: %s. The Directory Server will not listen for new connections on that address FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler defined in configuration entry %s was unable to create any of the socket channels on any of the configured addresses. This connection handler will be disabled ###FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection \ ### handler defined in configuration entry %s was unable to open a selector to \ ### allow it to multiplex the associated accept sockets: %s. This connection \ ### handler will be disabled ###SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection \ ### handler defined in configuration entry %s was unable to create a server \ ### socket channel to accept connections on %s:%d: %s. The Directory Server \ ### will not listen for new connections on that address ###FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler \ ### defined in configuration entry %s was unable to create any of the socket \ ### channels on any of the configured addresses. This connection handler will be \ ### disabled MILD_ERR_LDAP_CONNHANDLER_DENIED_CLIENT_180=La tentative de connexion du client %s \u00e0 %s a \u00e9t\u00e9 refus\u00e9e, car le client \u00e9tait inclus dans l'une des plages d'adresses refus\u00e9es MILD_ERR_LDAP_CONNHANDLER_DISALLOWED_CLIENT_181=La tentative de connexion du client %s \u00e0 %s a \u00e9t\u00e9 refus\u00e9e, car le client n'\u00e9tait pas inclus dans l'une des plages d'adresses autoris\u00e9es INFO_LDAP_CONNHANDLER_UNABLE_TO_REGISTER_CLIENT_182= Une erreur interne a emp\u00each\u00e9 Directory Server d'enregistrer correctement la connexion cliente de %s \u00e0 %s avec un gestionnaire de demandes appropri\u00e9\u00a0: %s MILD_ERR_LDAP_CONNHANDLER_CANNOT_ACCEPT_CONNECTION_183=Le gestionnaire de connexion LDAP d\u00e9fini dans l'entr\u00e9e de configuration %s n'a pas pu accepter une nouvelle connexion cliente\u00a0: %s FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP connection handler defined in configuration entry %s has experienced consecutive failures while trying to accept client connections: %s. This connection handler will be disabled FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler defined in configuration entry %s caught an unexpected error while trying to listen for new connections: %s. This connection handler will be disabled FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a selector to multiplex reads from clients: %s. This request handler cannot continue processing FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this client connection with the selector: %s FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could not be registered with a request handler because the Directory Server is shutting down FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could not be registered with a request handler because the pending queue associated with %s is too full FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client connection is being deregistered from the associated request handler because the Directory Server is shutting down ###FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP \ ### connection handler defined in configuration entry %s has experienced \ ### consecutive failures while trying to accept client connections: %s. This \ ### connection handler will be disabled ###FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler \ ### defined in configuration entry %s caught an unexpected error while trying to \ ### listen for new connections: %s. This connection handler will be disabled ###FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a \ ### selector to multiplex reads from clients: %s. This request handler cannot \ ### continue processing ###FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this \ ### client connection with the selector: %s ###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could \ ### not be registered with a request handler because the Directory Server is \ ### shutting down ###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could \ ### not be registered with a request handler because the pending queue associated \ ### with %s is too full ###FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client \ ### connection is being deregistered from the associated request handler because \ ### the Directory Server is shutting down MILD_ERR_ASN1_READER_MAX_SIZE_EXCEEDED_191=Impossible de d\u00e9coder les donn\u00e9es lues en tant qu'\u00e9l\u00e9ment ASN.1, car la longueur d'\u00e9l\u00e9ment d\u00e9cod\u00e9 de %d octets \u00e9tait plus importante que la longueur d'\u00e9l\u00e9ment autoris\u00e9e maximale de %d octets. Le flux d'entr\u00e9e sous-jacent a \u00e9t\u00e9 ferm\u00e9 et ce lecteur ne peut plus \u00eatre utilis\u00e9 MILD_ERR_LDAP_FILTER_STRING_NULL_192=Impossible de d\u00e9coder la cha\u00eene fournie en tant que filtre de recherche LDAP, car cette cha\u00eene \u00e9tait null MILD_ERR_LDAP_FILTER_UNCAUGHT_EXCEPTION_193=Impossible de d\u00e9coder la cha\u00eene fournie %s en tant que filtre de recherche LDAP, car une exception inattendue est apparue pendant le traitement\u00a0: %s @@ -218,9 +240,11 @@ MILD_ERR_LDAP_FILTER_NO_CORRESPONDING_OPEN_PARENTHESIS_198=Le filtre de recherche "%s" fourni n'a pas pu \u00eatre d\u00e9cod\u00e9 car aucune parenth\u00e8se ouvrante ne correspond \u00e0 la parenth\u00e8se fermante situ\u00e9e \u00e0 la position %d MILD_ERR_LDAP_FILTER_NO_CORRESPONDING_CLOSE_PARENTHESIS_199=Le filtre de recherche "%s" fourni n'a pas pu \u00eatre d\u00e9cod\u00e9 car aucune parenth\u00e8se fermante ne correspond \u00e0 la parenth\u00e8se ouvrante situ\u00e9e \u00e0 la position %d MILD_ERR_LDAP_FILTER_SUBSTRING_NO_ASTERISKS_200=Le filtre de recherche "%s" fourni n'a pas pu \u00eatre d\u00e9cod\u00e9 car aucun ast\u00e9risque (caract\u00e8re g\u00e9n\u00e9rique) n'est pr\u00e9sent dans la valeur de filtre de la sous-cha\u00eene probable entre les positions %d et %d MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_COLON_201=Le filtre de recherche "%s" fourni n'a pas pu \u00eatre d\u00e9cod\u00e9 car les deux points (:) permettant de d\u00e9limiter la fin du nom du type d'attribut ne sont pas pr\u00e9sents dans le composant de correspondance extensible commen\u00e7ant \u00e0 la position %d MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_COLON_201=Le filtre de recherche "%s" fourni n'a pas pu \u00eatre d\u00e9cod\u00e9 car la colonne permettant de d\u00e9limiter la fin du nom du type d'attribut n'est pas pr\u00e9sente dans le composant de correspondance extensible commen\u00e7ant \u00e0 la position %d MILD_ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPE_202=Arr\u00eat de cette connexion car le client a envoy\u00e9 un message incorrect de type %s (ID de message LDAP %d) qui n'est pas autoris\u00e9 pour les messages de demande SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated ###SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected \ ### failure occurred while trying to process a request of type %s (LDAP message \ ### ID %d): %s. The client connection will be terminated MILD_ERR_LDAP_INVALID_BIND_AUTH_TYPE_204=Le message de demande de liaison (ID de message LDAP %d ) contenait un type d'authentification incorrect %s. Il s'agit d'une erreur de protocole et cette connexion va \u00eatre arr\u00eat\u00e9e selon la section 4.2.3 de RFC 2251 MILD_ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERROR_205=Cette connexion cliente est en cours d'arr\u00eat car une erreur de protocole s'est produite lors de la tentative de traitement d'une demande de liaison. L'ID de message LDAP \u00e9tait %d et le message d'erreur pour la r\u00e9ponse de liaison \u00e9tait %s MILD_ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSE_206=Un message de r\u00e9ponse \u00e9tendu aurait \u00e9t\u00e9 envoy\u00e9 \u00e0 un client LDAPv2 (ID de connexion=%d, ID d'op\u00e9ration=%d) : %s. LDAPv2 n'autorise pas les op\u00e9rations \u00e9tendues, par cons\u00e9quent, cette r\u00e9ponse ne sera pas envoy\u00e9e @@ -230,43 +254,106 @@ MILD_ERR_LDAPV2_CLIENTS_NOT_ALLOWED_210=Directory Server a \u00e9t\u00e9 configur\u00e9 de mani\u00e8re \u00e0 refuser l'acc\u00e8s aux clients LDAPv2. Cette connexion va \u00eatre ferm\u00e9e MILD_ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWED_211=Le client avec l'ID de connexion %d a \u00e9t\u00e9 authentifi\u00e9 sur Directory Server \u00e0 l'aide de LDAPv2, mais il a tent\u00e9 d'envoyer une demande d'op\u00e9ration \u00e9tendue (ID message LDAP %d), ce qui n'est pas autoris\u00e9 pour les clients LDAPv2. La connexion va \u00eatre arr\u00eat\u00e9e MILD_ERR_LDAP_STATS_INVALID_MONITOR_INITIALIZATION_212=Une tentative d'initialisation du fournisseur du moniteur de statistiques LDAP a eu lieu, comme d\u00e9fini dans l'entr\u00e9e de configuration %s. Ce fournisseur de moniteur doit \u00eatre cr\u00e9\u00e9 uniquement dynamiquement dans Directory Server m\u00eame, et pas \u00e0 partir de la configuration SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request handler thread "%s" encountered an unexpected error that would have caused the thread to die: %s. The error has been caught and the request handler should continue operating as normal ###SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request \ ### handler thread "%s" encountered an unexpected error that would have caused \ ### the thread to die: %s. The error has been caught and the request handler \ ### should continue operating as normal MILD_ERR_LDAP_CONNHANDLER_REJECTED_BY_SERVER_214=Tentative d'enregistrement de cette connexion avec Directory Server rejet\u00e9e. Cela peut indiquer que le serveur dispose d\u00e9j\u00e0 du nombre maximal autoris\u00e9 de connexions concurrentes \u00e9tabli, ou qu'il est en mode d'acc\u00e8s restreint INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_ADDRESS_215=Adresse ou jeu d'adresses sur lequel ce gestionnaire de connexion peut accepter des connexions clientes. Si aucune valeur n'est sp\u00e9cifi\u00e9e, alors le serveur accepte les connexions sur toutes les adresses actives. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_216=Port TCP sur lequel ce gestionnaire de connexion peut accepter des connexions clientes. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOWED_CLIENTS_217=Sp\u00e9cifie un jeu de masques d'adresse qui peut servir \u00e0 d\u00e9terminer les adresses des clients autoris\u00e9s \u00e0 \u00e9tablir des connexions \u00e0 ce gestionnaire de connexion. Si aucune valeur n'est sp\u00e9cifi\u00e9e, alors tous les clients disposant d'adresses qui ne correspondent pas \u00e0 une adresse sur la liste de refus seront autoris\u00e9es. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais n'interf\u00e9reront pas avec des connexions \u00e9ventuellement d\u00e9j\u00e0 \u00e9tablies INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_ADDRESS_215=Adresse ou jeu d'adresses sur lequel ce gestionnaire de connexion peut accepter des connexions clientes. Si aucune valeur n'est sp\u00e9cifi\u00e9e, alors le serveur accepte les connexions sur toutes les adresses actives. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_216=Port TCP sur lequel ce gestionnaire de connexion peut accepter des connexions clientes. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOWED_CLIENTS_217=Sp\u00e9cifie un jeu de masques d'adresse qui peut servir \u00e0 d\u00e9terminer les adresses des clients autoris\u00e9s \u00e0 \u00e9tablir des connexions \u00e0 ce gestionnaire de connexion. Si aucune valeur n'est sp\u00e9cifi\u00e9e, alors tous les clients disposant d'adresses qui ne correspondent pas \u00e0 une adresse sur la liste de refus seront autoris\u00e9es. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais n'interf\u00e9reront pas avec des connexions \u00e9ventuellement d\u00e9j\u00e0 \u00e9tablies. INFO_LDAP_CONNHANDLER_DESCRIPTION_DENIED_CLIENTS_218=Sp\u00e9cifie un jeu de masques d'adresse qui peut servir \u00e0 d\u00e9terminer le jeu d'adresses des clients qui ne sont pas autoris\u00e9s \u00e0 \u00e9tablir des connexions \u00e0 ce gestionnaire de connexion. Si les masques de client autoris\u00e9s et refus\u00e9s sont d\u00e9finis et qu'une connexion cliente correspond \u00e0 un ou plusieurs masques dans les deux listes, alors la connexion est refus\u00e9e. Si seulement une liste de refus est sp\u00e9cifi\u00e9e, alors tout client qui ne correspond pas \u00e0 un masque dans cette liste est autoris\u00e9. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais n'interf\u00e9reront pas avec des connexions \u00e9ventuellement d\u00e9j\u00e0 \u00e9tablies INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_LDAPV2_219=Indique si les communications avec des clients LDAPv2 sont autoris\u00e9es. LDAPv2 est consid\u00e9r\u00e9 comme un protocole obsol\u00e8te et les clients qui l'utilisent ne seront pas autoris\u00e9s \u00e0 tirer profit de toutes les fonctions propos\u00e9es par le serveur. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais n'interf\u00e9reront pas avec des connexions \u00e9ventuellement d\u00e9j\u00e0 \u00e9tablies. INFO_LDAP_CONNHANDLER_DESCRIPTION_NUM_REQUEST_HANDLERS_220=Nombre de threads qui devraient \u00eatre utilis\u00e9s pour lire des demandes de clients et les placer dans la file d'attente de travail pour leur traitement. Sur les syst\u00e8mes importants qui acceptent de nombreuses demandes concurrentes, il peut \u00eatre efficace de disposer de plusieurs threads qui lisent les demandes de clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_SEND_REJECTION_NOTICE_221=Indique si envoyer un avis LDAPv3 de message de d\u00e9connexion aux connexions clientes rejet\u00e9es avant la fermeture de la connexion. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_LDAP_CONNHANDLER_DESCRIPTION_USE_TCP_KEEPALIVE_222=Indique si utiliser la fonction TCP KeepAlive pour les connexions clientes \u00e9tablies via ce gestionnaire de connexion. Ceci est recommand\u00e9, car cela peut aider le serveur \u00e0 d\u00e9tecter des connexions clientes qui ne sont plus valides, et aider \u00e0 \u00e9viter que les p\u00e9riph\u00e9riques r\u00e9seau interm\u00e9diaires ferment des connexions en raison d'un manque de communication. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais ne seront appliqu\u00e9es qu'aux connexions \u00e9tablies apr\u00e8s la modification. INFO_LDAP_CONNHANDLER_DESCRIPTION_USE_TCP_NODELAY_223=Indique si utiliser la fonction TCP NoDelay pour les connexions clientes \u00e9tablies via ce gestionnaire de connexion. Ceci est recommand\u00e9, car cela permet g\u00e9n\u00e9ralement d'obtenir des r\u00e9ponses plus rapides pour les clients, m\u00eame si des r\u00e9pertoires qui traitent fr\u00e9quemment des recherches qui correspondent \u00e0 plusieurs entr\u00e9es peuvent obtenir un d\u00e9bit plus \u00e9lev\u00e9 si cette fonction est d\u00e9sactiv\u00e9e. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais ne seront appliqu\u00e9es qu'aux connexions \u00e9tablies apr\u00e8s la modification. INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_REUSE_ADDRESS_224=Indique si l'option de socket SO_REUSEADDR doit \u00eatre utilis\u00e9e pour le socket qui accepte des connexions pour ce gestionnaire de connexion. Elle doit g\u00e9n\u00e9ralement \u00eatre activ\u00e9e, sauf mention contraire des ing\u00e9nieurs de support. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_REUSE_ADDRESS_224=Indique si l'option de socket SO_REUSEADDR doit \u00eatre utilis\u00e9e pour le socket qui accepte des connexions pour ce gestionnaire de connexion. Elle doit g\u00e9n\u00e9ralement \u00eatre activ\u00e9e, sauf mention contraire des ing\u00e9nieurs de support. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_MAX_REQUEST_SIZE_225=Taille maximale en octets autoris\u00e9e lors de la lecture de demandes de clients. Cela peut servir \u00e0 emp\u00eacher le refus de service de la part de clients qui envoient des demandes extr\u00eamement importantes. Une valeur z\u00e9ro indique qu'aucune limite doit \u00eatre impos\u00e9e. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte INFO_LDAP_CONNHANDLER_DESCRIPTION_USE_SSL_226=Indique si ce gestionnaire de connexion doit utiliser SSL lors de l'acceptation de connexions de clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_USE_SSL_226=Indique si ce gestionnaire de connexion doit utiliser SSL lors de l'acceptation de connexions de clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_STARTTLS_227=Indique si ce gestionnaire de connexion doit autoriser des clients \u00e0 utiliser l'op\u00e9ration \u00e9tendue StartTLS pour initier une communication s\u00e9curis\u00e9e via une connexion LDAP non SSL. Cela ne peut pas \u00eatre utilis\u00e9 si SSL est activ\u00e9 pour le gestionnaire de connexion. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte pour les clients LDAP INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CLIENT_AUTH_POLICY_228=Strat\u00e9gie qui doit \u00eatre utilis\u00e9e concernant la demande ou l'exigence aupr\u00e8s du client de pr\u00e9senter son propre certificat lors de l'\u00e9tablissement d'une connexion SSL, ou de l'utilisation de StartTLS pour d\u00e9marrer un canal s\u00e9curis\u00e9 dans une connexion \u00e9tablie. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_229=Pseudonyme du certificat que doit utiliser le gestionnaire de connexion lors de l'acceptation de connexions SSL ou de l'ex\u00e9cution d'une n\u00e9gociation StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen address "%s" in configuration entry "%s" could not be resolved: %s. Please make sure that name resolution is properly configured on this system SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected error occurred while processing the ds-cfg-listen-address attribute in configuration entry %s, which is used to specify the address or set of addresses on which to listen for client connections: %s SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An unexpected error occurred while processing the ds-cfg-allowed-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are allowed to establish connections to this connection handler: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected error occurred while processing the ds-cfg-denied-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are not allowed to establish connections to this connection handler: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected error occurred while processing the ds-cfg-allow-ldap-v2 attribute in configuration entry %s, which is used to indicate whether LDAPv2 clients will be allowed to access this connection handler: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An unexpected error occurred while processing the ds-cfg-num-request-handlers attribute in configuration entry %s, which is used to specify the number of request handlers to use to read requests from clients: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=An unexpected error occurred while processing the ds-cfg-send-rejection-notice attribute in configuration entry %s, which is used to indicate whether to send a notice of disconnection message to rejected client connections: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive attribute in configuration entry %s, which is used to periodically send TCP Keep-Alive messages over idle connections: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An unexpected error occurred while processing the ds-cfg-use-tcp-no-delay attribute in configuration entry %s, which is used to determine whether to immediately flush responses to clients: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address attribute in configuration entry %s, which is used to determine whether to set the SO_REUSEADDR option on the listen socket: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An unexpected error occurred while processing the ds-cfg-max-request-size attribute in configuration entry %s, which is used to determine the maximum size in bytes that can be used for a client request: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP connection handler defined in configuration entry %s is configured to communicate over SSL and also to allow clients to use the StartTLS extended operation. These options can not be used at the same time, so clients will not be allowed to use the StartTLS operation SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected error occurred while processing the ds-cfg-allow-start-tls attribute in configuration entry %s, which is used to indicate whether clients can use the StartTLS extended operation: %s SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client authentication policy "%s" specified in attribute ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The value must be one of "disabled", "optional", or "required" SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy attribute in configuration entry %s, which is used to specify the policy that should be used for requesting/requiring SSL client authentication: %s SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in attribute %s of configuration entry %s could not be decoded as a valid address mask: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CLIENT_AUTH_POLICY_228=Strat\u00e9gie qui doit \u00eatre utilis\u00e9e concernant la demande ou l'exigence aupr\u00e8s du client de pr\u00e9senter son propre certificat lors de l'\u00e9tablissement d'une connexion SSL, ou de l'utilisation de StartTLS pour d\u00e9marrer un canal s\u00e9curis\u00e9 dans une connexion \u00e9tablie. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_229=Pseudonyme du certificat que doit utiliser le gestionnaire de connexion lors de l'acceptation de connexions SSL ou de l'ex\u00e9cution d'une n\u00e9gociation StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen \ ### address "%s" in configuration entry "%s" could not be resolved: %s. Please \ ### make sure that name resolution is properly configured on this system ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected \ ### error occurred while processing the ds-cfg-listen-address attribute in \ ### configuration entry %s, which is used to specify the address or set of \ ### addresses on which to listen for client connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined \ ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ ### required attribute ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected \ ### error occurred while processing the ds-cfg-listen-port attribute in \ ### configuration entry %s, which is used to specify the port on which to listen \ ### for client connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An \ ### unexpected error occurred while processing the ds-cfg-allowed-client \ ### attribute in configuration entry %s, which is used to specify the address \ ### mask(s) of the clients that are allowed to establish connections to this \ ### connection handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected \ ### error occurred while processing the ds-cfg-denied-client attribute in \ ### configuration entry %s, which is used to specify the address mask(s) of the \ ### clients that are not allowed to establish connections to this connection \ ### handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected \ ### error occurred while processing the ds-cfg-allow-ldap-v2 attribute in \ ### configuration entry %s, which is used to indicate whether LDAPv2 clients will \ ### be allowed to access this connection handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An \ ### unexpected error occurred while processing the ds-cfg-num-request-handlers \ ### attribute in configuration entry %s, which is used to specify the number of \ ### request handlers to use to read requests from clients: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=An \ ### unexpected error occurred while processing the ds-cfg-send-rejection-notice \ ### attribute in configuration entry %s, which is used to indicate whether to \ ### send a notice of disconnection message to rejected client connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An \ ### unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive \ ### attribute in configuration entry %s, which is used to periodically send TCP \ ### Keep-Alive messages over idle connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An \ ### unexpected error occurred while processing the ds-cfg-use-tcp-no-delay \ ### attribute in configuration entry %s, which is used to determine whether to \ ### immediately flush responses to clients: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An \ ### unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address \ ### attribute in configuration entry %s, which is used to determine whether to \ ### set the SO_REUSEADDR option on the listen socket: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An \ ### unexpected error occurred while processing the ds-cfg-max-request-size \ ### attribute in configuration entry %s, which is used to determine the maximum \ ### size in bytes that can be used for a client request: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error \ ### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ ### %s, which is used to indicate whether to use SSL when accepting client \ ### connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP \ ### connection handler defined in configuration entry %s is configured to \ ### communicate over SSL and also to allow clients to use the StartTLS extended \ ### operation. These options can not be used at the same time, so clients will \ ### not be allowed to use the StartTLS operation ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected \ ### error occurred while processing the ds-cfg-allow-start-tls attribute in \ ### configuration entry %s, which is used to indicate whether clients can use the \ ### StartTLS extended operation: %s ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client \ ### authentication policy "%s" specified in attribute \ ### ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The \ ### value must be one of "disabled", "optional", or "required" ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An \ ### unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy \ ### attribute in configuration entry %s, which is used to specify the policy that \ ### should be used for requesting/requiring SSL client authentication: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An \ ### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ ### attribute in configuration entry %s, which is used to specify the nickname of \ ### the certificate to use for accepting SSL/TLS connections: %s ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in \ ### attribute %s of configuration entry %s could not be decoded as a valid \ ### address mask: %s INFO_LDAP_CONNHANDLER_NEW_ALLOWED_CLIENTS_250=Un nouveau jeu de masques d'adresse clients autoris\u00e9s a \u00e9t\u00e9 appliqu\u00e9 \u00e0 l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_NEW_DENIED_CLIENTS_251=Un nouveau jeu de masques d'adresse clients refus\u00e9s a \u00e9t\u00e9 appliqu\u00e9 \u00e0 l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_NEW_ALLOW_LDAPV2_252=La valeur de l'attribut ds-cfg-allow-ldap-v2 a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s @@ -276,16 +363,26 @@ INFO_LDAP_CONNHANDLER_NEW_MAX_REQUEST_SIZE_256=La valeur de l'attribut ds-cfg-max-request-size a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_NEW_ALLOW_STARTTLS_257=La valeur de l'attribut ds-cfg-allow-start-tls a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_DESCRIPTION_KEEP_STATS_258=Indique si le gestionnaire de connexion doit conserver de statistiques concernant la communication cliente LDAP. La conservation de ces informations peut entra\u00eener une l\u00e9g\u00e8re baisse des performances, mais peut se r\u00e9v\u00e9ler utile \u00e0 la compr\u00e9hension des types d'usage des clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte, mais ne s'appliqueront qu'aux nouvelles connxions, tout en ayant pour effet secondaire d'effacer toute donn\u00e9es statistique existante qui aurait pu \u00eatre collect\u00e9e SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected error occurred while processing the ds-cfg-keep-stats attribute in configuration entry %s, which is used to indicate whether LDAP usage statistics should be enabled for this connection handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected \ ### error occurred while processing the ds-cfg-keep-stats attribute in \ ### configuration entry %s, which is used to indicate whether LDAP usage \ ### statistics should be enabled for this connection handler: %s INFO_LDAP_CONNHANDLER_NEW_KEEP_STATS_260=La valeur de l'attribut ds-cfg-keep-stats a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s MILD_ERR_ASN1_LONG_SET_VALUE_INVALID_LENGTH_261=Impossible de d\u00e9coder le tableau d'octets fourni en tant que valeur d'un \u00e9l\u00e9ment long ASN.1, car ce tableau ne poss\u00e9dait pas une longueur comprise entre 1 et 8 octets (la longueur fournie \u00e9tait de %d) MILD_ERR_ASN1_LONG_DECODE_ELEMENT_INVALID_LENGTH_262=Impossible de d\u00e9coder l'\u00e9l\u00e9ment ASN.1 fourni en tant qu'\u00e9l\u00e9ment long, car la longueur de la valeur d'\u00e9l\u00e9ment n'\u00e9tait pas comprise entre un et huit octets (la longueur r\u00e9elle \u00e9tait de %d) MILD_ERR_ASN1_LONG_DECODE_ARRAY_INVALID_LENGTH_263=Impossible de d\u00e9coder le tableau d'octets fournis en tant qu'\u00e9l\u00e9ment long ASN.1, car la longueur de la valeur d\u00e9cod\u00e9e n'\u00e9tait pas comprise entre 1 et 8 octets (la longueur d\u00e9cod\u00e9e \u00e9tait de %d) SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while trying to decode the DN %s used for internal operations as a root user: %s ###SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while \ ### trying to decode the DN %s used for internal operations as a root user: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_PROTOCOLS_265=Noms des protocoles SSL qui seront autoris\u00e9s pour une utilisation dans une communication SSL ou StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte mais n'auront un impact que sur les nouvelles sessions SSL/TLS cr\u00e9\u00e9es apr\u00e8s la modification SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL protocols to allow for SSL/TLS sessions: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected \ ### error occurred while processing the ds-cfg-ssl-protocol attribute in \ ### configuration entry %s, which is used to specify the names of the SSL \ ### protocols to allow for SSL/TLS sessions: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_CIPHERS_267=Noms des suites de chiffrement SSL qui seront autoris\u00e9es pour une utilisation dans une communication SSL ou StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte mais n'auront un impact que sur les nouvelles sessions SSL/TLS cr\u00e9\u00e9es apr\u00e8s la modification SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL cipher suites to allow for SSL/TLS sessions: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected \ ### error occurred while processing the ds-cfg-ssl-protocol attribute in \ ### configuration entry %s, which is used to specify the names of the SSL cipher \ ### suites to allow for SSL/TLS sessions: %s INFO_LDAP_CONNHANDLER_NEW_SSL_PROTOCOLS_269=La valeur de l'attribut ds-cfg-ssl-protocol a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_NEW_SSL_CIPHERS_270=La valeur de l'attribut ds-cfg-ssl-cipher-suite a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s MILD_ERR_LDAP_TLS_EXISTING_SECURITY_PROVIDER_271=Impossible d'activer le fournisseur de s\u00e9curit\u00e9 de connexion TLS sur cette connexion cliente, car elle utilise d\u00e9j\u00e0 le fournisseur %s. StartTLS peut uniquement \u00eatre utilis\u00e9e sur des connexions de texte en clair @@ -336,47 +433,117 @@ MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_OID_316=Une erreur s'est produite lors de la tentative de d\u00e9codage de l'OID de r\u00e9ponse interm\u00e9diaire\u00a0: %s MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_VALUE_317=Une erreur s'est produite lors de la tentative de d\u00e9codage de la valeur de r\u00e9ponse interm\u00e9diaire\u00a0: %s MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_INVALID_ELEMENT_TYPE_318=L'\u00e9l\u00e9ment de s\u00e9quence de r\u00e9ponses interm\u00e9diaires contenait un type BER incorrect %s, inappropri\u00e9 pour l'OID ou la valeur INFO_LDAP_CONNHANDLER_DESCRIPTION_BACKLOG_319=Taille de files d'attente d'acceptation qui contr\u00f4le le nombre de nouvelles tentatives de connexion pouvant \u00eatre autoris\u00e9es dans le journal des connexions en attente avant d'\u00eatre rejet\u00e9es. Cela doit uniquement \u00eatre modifi\u00e9 s'il est pr\u00e9vu que Directory Server re\u00e7oive un nombre de nouvelles tentatives de connexion important en m\u00eame temps. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error occurred while processing the ds-cfg-accept-backlog attribute in configuration entry %s, which is used to specify the accept backlog size: %s SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter "%s" cannot be used as a matched values filter because filters of type %s are not allowed for use in matched values filters SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter "%s" cannot be used as a matched values filter because it is an extensible match filter that contains the dnAttributes flag, which is not allowed for matched values filters SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values filter could not be decoded because there were an invalid number of elements in the attribute value assertion (expected 2, got %d) SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting to decode the attribute value assertion in the provided matched values filter: %s SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched values filter could not be decoded because there were an invalid number of elements in the substring sequence (expected 2, got %d) SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values filter could not be decoded because there were no subInitial, subAny, or subFinal components in the substring filter SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values filter could not be decoded because there were multiple subInitial components in the substring filter SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter could not be decoded because there were multiple subFinal components in the substring filter SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched values filter could not be decoded because there was an invalid element of type %s in the substring filter SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values filter could not be decoded because an error occurred while decoding the substring filter component: %s SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched values filter could not be decoded because an error occurred while decoding the presence filter component: %s SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched values filter could not be decoded because there were an invalid number of elements in the extensible match sequence (expected 2 or 3, found %d) SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched values filter could not be decoded because there were multiple matching rule ID elements found in the extensible match filter sequence SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values filter could not be decoded because there were multiple attribute type elements found in the extensible match filter sequence SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values filter could not be decoded because there were multiple assertion value elements found in the extensible match filter sequence SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched values filter could not be decoded because there was an invalid element of type %s in the extensible match filter SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched values filter could not be decoded because an error occurred while decoding the extensible match filter component: %s SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values filter could not be decoded because it had an invalid BER type of %s SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided matched values control because it does not have a value SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode the provided matched values control because an error occurred while attempting to decode the value as an ASN.1 sequence: %s SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched values control because the control value does not specify any filters for use in matching attribute values SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided control as a password expired control because the provided control had a value that could not be parsed as an integer SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided password expiring control because it does not have a value SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot decode the provided control as a password expiring control because an error occurred while attempting to decode the number of seconds until expiration: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_BACKLOG_319=Taille de files d'attente d'acceptation qui contr\u00f4le le nombre de nouvelles tentatives de connexion pouvant \u00eatre autoris\u00e9es dans le journal des connexions en attente avant d'\u00eatre rejet\u00e9es. Cela doit uniquement \u00eatre modifi\u00e9 s'il est pr\u00e9vu que Directory Server re\u00e7oive un nombre de nouvelles tentatives de connexion important en m\u00eame temps. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error \ ### occurred while processing the ds-cfg-accept-backlog attribute in \ ### configuration entry %s, which is used to specify the accept backlog size: %s ###SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter \ ### "%s" cannot be used as a matched values filter because filters of type %s are \ ### not allowed for use in matched values filters ###SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter \ ### "%s" cannot be used as a matched values filter because it is an extensible \ ### match filter that contains the dnAttributes flag, which is not allowed for \ ### matched values filters ###SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values \ ### filter could not be decoded because there were an invalid number of elements \ ### in the attribute value assertion (expected 2, got %d) ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting \ ### to decode the attribute value assertion in the provided matched values \ ### filter: %s ###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched \ ### values filter could not be decoded because there were an invalid number of \ ### elements in the substring sequence (expected 2, got %d) ###SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values \ ### filter could not be decoded because there were no subInitial, subAny, or \ ### subFinal components in the substring filter ###SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values \ ### filter could not be decoded because there were multiple subInitial components \ ### in the substring filter ###SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter \ ### could not be decoded because there were multiple subFinal components in the \ ### substring filter ###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched \ ### values filter could not be decoded because there was an invalid element of \ ### type %s in the substring filter ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values \ ### filter could not be decoded because an error occurred while decoding the \ ### substring filter component: %s ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched \ ### values filter could not be decoded because an error occurred while decoding \ ### the presence filter component: %s ###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched \ ### values filter could not be decoded because there were an invalid number of \ ### elements in the extensible match sequence (expected 2 or 3, found %d) ###SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched \ ### values filter could not be decoded because there were multiple matching rule \ ### ID elements found in the extensible match filter sequence ###SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values \ ### filter could not be decoded because there were multiple attribute type \ ### elements found in the extensible match filter sequence ###SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values \ ### filter could not be decoded because there were multiple assertion value \ ### elements found in the extensible match filter sequence ###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched \ ### values filter could not be decoded because there was an invalid element of \ ### type %s in the extensible match filter ###SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched \ ### values filter could not be decoded because an error occurred while decoding \ ### the extensible match filter component: %s ###SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values \ ### filter could not be decoded because it had an invalid BER type of %s ###SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided \ ### matched values control because it does not have a value ###SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode \ ### the provided matched values control because an error occurred while \ ### attempting to decode the value as an ASN.1 sequence: %s ###SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched \ ### values control because the control value does not specify any filters for use \ ### in matching attribute values ###SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided \ ### control as a password expired control because the provided control had a \ ### value that could not be parsed as an integer ###SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided \ ### password expiring control because it does not have a value ###SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot \ ### decode the provided control as a password expiring control because an error \ ### occurred while attempting to decode the number of seconds until expiration: \ ### %s MILD_WARN_LDAP_CLIENT_DUPLICATE_MESSAGE_ID_345=Directory Server est d\u00e9j\u00e0 en train de traiter une autre demande sur la m\u00eame connexion cliente avec le m\u00eame ID message %d MILD_WARN_LDAP_CLIENT_CANNOT_ENQUEUE_346=Directory Server a rencontr\u00e9 une erreur inattendue lors de la tentative d'ajout de la demande cliente \u00e0 la file d'attente de travail\u00a0: %s INFO_JMX_CONNHANDLER_DESCRIPTION_LISTEN_PORT_347=Port TCP sur lequel ce gestionnaire de connexion peut accepter des connexions administratives. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_USE_SSL_350=Indique si ce gestionnaire de connexion doit utiliser SSL lors de l'acceptation de connexions de clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_352=Pseudonyme du certificat que doit utiliser le gestionnaire de connexion lors de l'acceptation de connexions SSL ou de l'ex\u00e9cution d'une n\u00e9gociation StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided control as a password policy request control because the provided control had a value but the password policy request control should not have a value SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided password policy response control because it does not have a value SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided password policy response control because the warning element has an invalid type of %s SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided password policy response control because the error element has an invalid type of %d SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided password policy response control because the value sequence has an element with an invalid type of %s SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password policy response control: %s INFO_JMX_CONNHANDLER_DESCRIPTION_LISTEN_PORT_347=Port TCP sur lequel ce gestionnaire de connexion peut accepter des connexions administratives. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined \ ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ ### required attribute ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected \ ### error occurred while processing the ds-cfg-listen-port attribute in \ ### configuration entry %s, which is used to specify the port on which to listen \ ### for client connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_USE_SSL_350=Indique si ce gestionnaire de connexion doit utiliser SSL lors de l'acceptation de connexions de clients. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error \ ### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ ### %s, which is used to indicate whether to use SSL when accepting client \ ### connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_352=Pseudonyme du certificat que doit utiliser le gestionnaire de connexion lors de l'acceptation de connexions SSL ou de l'ex\u00e9cution d'une n\u00e9gociation StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An \ ### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ ### attribute in configuration entry %s, which is used to specify the nickname of \ ### the certificate to use for accepting SSL/TLS connections: %s ###SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided \ ### control as a password policy request control because the provided control had \ ### a value but the password policy request control should not have a value ###SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided \ ### password policy response control because it does not have a value ###SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided \ ### password policy response control because the warning element has an invalid \ ### type of %s ###SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided \ ### password policy response control because the error element has an invalid \ ### type of %d ###SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided \ ### password policy response control because the value sequence has an element \ ### with an invalid type of %s ###SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password \ ### policy response control: %s INFO_PWPERRTYPE_DESCRIPTION_PASSWORD_EXPIRED_360=passwordExpired INFO_PWPERRTYPE_DESCRIPTION_ACCOUNT_LOCKED_361=accountLocked INFO_PWPERRTYPE_DESCRIPTION_CHANGE_AFTER_RESET_362=changeAfterReset @@ -392,35 +559,77 @@ MILD_ERR_PROXYAUTH1_UNUSABLE_ACCOUNT_372=L'utilisation du contr\u00f4le V1 d'autorisation en proxy pour l'utilisateur %s n'est pas autoris\u00e9e par la configuration de strat\u00e9gie de mot de passe MILD_ERR_PROXYAUTH2_CANNOT_LOCK_USER_373=Impossible d'obtenir un verrou sur l'entr\u00e9e utilisateur %s pour la validation de contr\u00f4le V2 d'autorisation en proxy MILD_ERR_PROXYAUTH2_UNUSABLE_ACCOUNT_374=L'utilisation du contr\u00f4le V2 d'autorisation en proxy pour l'utilisateur %s n'est pas autoris\u00e9e par la configuration de strat\u00e9gie de mot de passe SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided control as an account availability request control because the provided control had a value but the account availability request control should not have a value SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided account availability response control because it does not have a value SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account availability response control indicated that the account was unavailable but had an unknown unavailable element type of %s SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account availability response control had an unknown ACCOUNT_USABLE_RESPONSE element type of %s SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account availability response control: %s SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided address mask prefix because an invalid value was specified. The permitted values for IPv4are 0 to32 and for IPv6 0 to128 SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided address mask because an prefix mask was specified with an wild card "*" match character SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided address mask because the it has an invalid format ###SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided \ ### control as an account availability request control because the provided \ ### control had a value but the account availability request control should not \ ### have a value ###SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided \ ### account availability response control because it does not have a value ###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account \ ### availability response control indicated that the account was unavailable but \ ### had an unknown unavailable element type of %s ###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account \ ### availability response control had an unknown ACCOUNT_USABLE_RESPONSE element \ ### type of %s ###SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account \ ### availability response control: %s ###SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided \ ### address mask prefix because an invalid value was specified. The permitted \ ### values for IPv4are 0 to32 and for IPv6 0 to128 ###SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided \ ### address mask because an prefix mask was specified with an wild card "*" match \ ### character ###SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided \ ### address mask because the it has an invalid format MILD_ERR_LDAP_NO_CLEAR_SECURITY_PROVIDER_383=Le gestionnaire de connexion LDAP %s n'a pas pu envoyer de r\u00e9ponse en texte clair au client, car il ne poss\u00e8de pas de r\u00e9f\u00e9rence de fournisseur de s\u00e9curit\u00e9 de connexion claire MILD_ERR_LDAP_ATTRIBUTE_DUPLICATE_VALUES_384=L'attribut LDAP fourni %s contient des valeurs dupliqu\u00e9es MILD_ERR_LDAP_FILTER_UNKNOWN_MATCHING_RULE_385=Le filtre de recherche LDAP fourni %s contient des r\u00e9gles de correspondance inconnues MILD_ERR_LDAP_FILTER_VALUE_WITH_NO_ATTR_OR_MR_386=Le filtre de recherche LDAP fourni poss\u00e8de une valeur d'assertion mais ne contient pas de type d'attribut ni d'ID de r\u00e8gle correspondante FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call select() in the LDAP connection handler: %s. It appears that your JVM may be susceptible to the issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable to handle LDAP requests in its current configuration. Please upgrade to a newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) or set the number of available file descriptors to a value greater than or equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting the Directory Server ###FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call \ ### select() in the LDAP connection handler: %s. It appears that your JVM may \ ### be susceptible to the issue described at \ ### http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable \ ### to handle LDAP requests in its current configuration. Please upgrade to a \ ### newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) \ ### or set the number of available file descriptors to a value greater than or \ ### equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting \ ### the Directory Server MILD_ERR_PROXYAUTH1_CONTROL_NOT_CRITICAL_388=Traitement de la demande refus\u00e9, car celle-ci contient un contr\u00f4le V1 d'autorisation en proxy qui n'est pas indiqu\u00e9 comme critique. Le contr\u00f4le d'autorisation en proxy doit toujours poss\u00e9der une valeur critique "true" MILD_ERR_PROXYAUTH2_CONTROL_NOT_CRITICAL_389=Traitement de la demande refus\u00e9, car celle-ci contient un contr\u00f4le V2 d'autorisation en proxy qui n'est pas indiqu\u00e9 comme critique. Le contr\u00f4le d'autorisation en proxy doit toujours poss\u00e9der une valeur critique "true" INFO_LDAP_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_390=DN de l'entr\u00e9e de configuration pour le fournisseur du gestionnaire de cl\u00e9 devant \u00eatre utilis\u00e9 avec ce gestionnaire de connexion LDAP. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte, mais uniquement pour les tentatives suivantes d'acc\u00e8s au fournisseur du gestionnaire de cl\u00e9 pour les connexions clientes associ\u00e9es SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute ds-cfg-key-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled key manager provider SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the key manager provider for use with the LDAP connection handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute \ ### ds-cfg-key-manager-provider of configuration entry %s has an invalid value \ ### %s which does not reference an enabled key manager provider ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error \ ### occurred while processing the ds-cfg-key-manager-provider attribute in \ ### configuration entry %s, which is used to specify the key manager provider for \ ### use with the LDAP connection handler: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_TRUSTMANAGER_DN_393=DN de l'entr\u00e9e de configuration pour le fournisseur du gestionnaire d'approbation qui doit \u00eatre utilis\u00e9 avec ce gestionnaire de connexion LDAP. Les modifications apport\u00e9es \u00e0 cet attribut seront imm\u00e9diatement prises en compte, mais uniquement pour les tentatives suivantes d'acc\u00e8s au fournisseur du gestionnaire d'approbation pour les connexions clientes associ\u00e9es SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration attribute ds-cfg-trust-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled trust manager provider SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error occurred while processing the ds-cfg-trust-manager-provider attribute in configuration entry %s, which is used to specify the trust manager provider for use with the LDAP connection handler: %s ###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration \ ### attribute ds-cfg-trust-manager-provider of configuration entry %s has an \ ### invalid value %s which does not reference an enabled trust manager provider ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error \ ### occurred while processing the ds-cfg-trust-manager-provider attribute in \ ### configuration entry %s, which is used to specify the trust manager provider \ ### for use with the LDAP connection handler: %s INFO_LDAP_CONNHANDLER_NEW_KEYMANAGER_DN_396=La valeur de l'attribut ds-cfg-key-manager-provider a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s INFO_LDAP_CONNHANDLER_NEW_TRUSTMANAGER_DN_397=La valeur de l'attribut ds-cfg-trust-manager-provider a \u00e9t\u00e9 mise \u00e0 jour par %s dans l'entr\u00e9e de configuration %s INFO_JMX_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_398=DN du fournisseur du gestionnaire de cl\u00e9 que doit utiliser le gestionnaire de connexion lors de l'acceptation de connexions SSL ou de l'ex\u00e9cution d'une n\u00e9gociation StartTLS. Les modifications apport\u00e9es \u00e0 cet attribut de configuration seront imm\u00e9diatement prises en compte SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, because the provided key manager DN %s does not refer to an enabled key manager provider SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the DN of the key manager provider to use for accepting SSL/TLS connections: %s ###SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while \ ### processing the ds-cfg-key-manager-provider attribute in configuration \ ### entry %s, because the provided key manager DN %s does not refer to an enabled \ ### key manager provider ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected \ ### error occurred while processing the ds-cfg-key-manager-provider attribute \ ### in configuration entry %s, which is used to specify the DN of the key manager \ ### provider to use for accepting SSL/TLS connections: %s MILD_ERR_LDAP_CONNHANDLER_CANNOT_SET_SECURITY_PROVIDER_401=Une erreur s'est produite lors de la tentative de configuration du fournisseur de s\u00e9curit\u00e9 de connexion pour la connexion cliente : %s SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which key manager provider should be used SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which trust manager provider should be used ###SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler \ ### defined in configuration entry %s is configured to use either SSL or \ ### StartTLS, but does not specify which key manager provider should be used ###SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection \ ### handler defined in configuration entry %s is configured to use either SSL or \ ### StartTLS, but does not specify which trust manager provider should be used INFO_LDAPS_CONNHANDLER_DESCRIPTION_ENABLE_404=Indique si le gestionnaire de connexion LDAPS doit \u00eatre activ\u00e9 MILD_ERR_LDAP_FILTER_NOT_EXACTLY_ONE_405=Impossible de d\u00e9coder le filtre de recherche fourni "%s" car le filtre NOT situ\u00e9 entre %d et %d ne contient pas exactement un composant de filtre INFO_SORTREQ_CONTROL_NO_VALUE_406=Impossible de d\u00e9coder le contr\u00f4le fourni en tant que contr\u00f4le de demande de tri c\u00f4t\u00e9 serveur, car il ne contient pas de valeur de contr\u00f4le @@ -441,7 +650,7 @@ INFO_VLVRES_CONTROL_NO_VALUE_421=Impossible de d\u00e9coder le contr\u00f4le fourni en tant que contr\u00f4le de r\u00e9ponse VLV, car il ne contient pas de valeur de contr\u00f4le INFO_VLVRES_CONTROL_INVALID_ELEMENT_COUNT_422=Impossible de d\u00e9coder le contr\u00f4le fourni en tant que contr\u00f4le de r\u00e9ponse VLV, car il contient un nombre d'\u00e9l\u00e9ments incorrect : %d INFO_VLVRES_CONTROL_CANNOT_DECODE_VALUE_423=Impossible de traiter le contr\u00f4le de r\u00e9ponse VLV fourni, car une erreur s'est produite lors de la tentative de d\u00e9codage de la valeur du contr\u00f4le : %s INFO_GETEFFECTIVERIGHTS_INVALID_AUTHZID_424=L'ID d'autorisation "%s" contenu dans le contr\u00f4le geteffectiverights est invalide car il ne doit pas commencer par "dn:" pour indiquer un DN utilisateur INFO_GETEFFECTIVERIGHTS_INVALID_AUTHZID_424=L'ID d'autorisation "%s" contenu dans le contr\u00f4le geteffectiverights est incorrect, car il ne commence pas par "dn:" pour indiquer un DN utilisateur INFO_GETEFFECTIVERIGHTS_DECODE_ERROR_425=Impossible de d\u00e9coder le contr\u00f4le de demande geteffectiverights fourni : %s INFO_CANNOT_DECODE_GETEFFECTIVERIGHTS_AUTHZID_DN_426=Impossible de d\u00e9coder la cha\u00eene de DN authzid "%s" en tant que nom distinctif valide\u00a0: %s MILD_ERR_LDAP_FILTER_ENCLOSED_IN_APOSTROPHES_427=Un filtre LDAP entre apostrophes est incorrect\u00a0: %s @@ -449,8 +658,10 @@ MILD_ERR_LDAP_FILTER_INVALID_CHAR_IN_ATTR_TYPE_429=Le filtre de recherche fourni contient un type d'attribut incorrect '%s' avec un caract\u00e8re incorrect '%s' \u00e0 la position %d MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_430=Impossible de d\u00e9coder le filtre de recherche fourni "%s" car le composant de correspondance extensible commen\u00e7ant \u00e0 l'emplacement %d n'inclut ni description d'attribut ni ID de r\u00e8gle de correspondance. L'un d'eux au moins doit \u00eatre fourni MILD_ERR_LDAPV2_CONTROLS_NOT_ALLOWED_431=Les clients LDAPv2 ne sont pas autoris\u00e9s \u00e0 utiliser des contr\u00f4les de demande SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler defined in configuration entry %s was unable to bind to %s:%d: %s SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined in configuration entry %s was unable to bind to port %d: %s ###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler \ ### defined in configuration entry %s was unable to bind to %s:%d: %s ###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined \ ### in configuration entry %s was unable to bind to port %d: %s MILD_ERR_JMX_ADD_INSUFFICIENT_PRIVILEGES_434=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations d'ajout via JMX MILD_ERR_JMX_DELETE_INSUFFICIENT_PRIVILEGES_435=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations de suppression via JMX MILD_ERR_JMX_MODIFY_INSUFFICIENT_PRIVILEGES_436=Vous ne disposez pas des privil\u00e8ges suffisants pour effectuer des op\u00e9rations de modification via JMX @@ -462,7 +673,11 @@ MILD_ERR_INTERNALOS_INVALID_REQUEST_442=Le message LDAP fourni poss\u00e9dait un type d'op\u00e9ration incorrect (%s) pour une demande MILD_ERR_INTERNALOS_SASL_BIND_NOT_SUPPORTED_443=Les op\u00e9rations SASL bind ne sont pas prises en charge via des sockets LDAP internes MILD_ERR_INTERNALOS_STARTTLS_NOT_SUPPORTED_444=Les op\u00e9rations Start TLS ne sont pas prises en charge via des sockets LDAP internes SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directory ###SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s \ ### specified as the LDIF directory path for the LDIF connection handler defined \ ### in configuration entry %s exists but is not a directory. The specified path \ ### must be a directory. The LDIF connection handler will start, but will not \ ### be able to proces any changes until this path is changed to a directory MILD_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSING_446=Le r\u00e9pertoire %s r\u00e9f\u00e9rence par le gestionnaire de connexion LDIF d\u00e9fini dans l'entr\u00e9e de configuration %s n'existe pas. Le gestionnaire de connexion LDIF va d\u00e9marrer, mais il ne pourra pas traiter les modifications tant que ce r\u00e9pertoire n'est pas cr\u00e9\u00e9 MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL_447=Une erreur s'est produite lors d'une tentative de lire un enregistrement de modification \u00e0 partir du fichier LDIF\u00a0: %s. Cette modification est ignor\u00e9e mais le traitement des fichiers LDIF continue MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL_448=Une ereur s'est produite lors d'une tentative de lire un enregistrement de modification \u00e0 partir du fichier LDIF\u00a0: %s. Aucun traitement ult\u00e9rieur sur ce fichier LDIF ne peut \u00eatre effectu\u00e9 @@ -471,26 +686,54 @@ INFO_LDIF_CONNHANDLER_ERROR_MESSAGE_451=Informations suppl\u00e9mentaires\u00a0: %s INFO_LDIF_CONNHANDLER_MATCHED_DN_452=DN correspondant\u00a0: %s INFO_LDIF_CONNHANDLER_REFERRAL_URL_453=URL de r\u00e9f\u00e9rence\u00a0: %s SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use INFO_SNMP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_1458=Port SNMP sur lequel le gestionnaire de connexion accepte les demandes SNMP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected error occurred when this connection handler started SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined for this connection handler. The configuration parameters ds-cfg-listen-port and ds-cfg-trap-port are required by the connection handler to start SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is an unknown host. Traps will not be sent to this destination SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the appropriate OpenDMK jar files to enable the SNMP Connection Handler. Please go under http://opendmk.dev.java.net and set the opendmk-jarfile configuration parameter to set the full path of the required jdmkrt.jar file. The SNMP connection Handler didn't started SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=Cannot initialize the SNMP Connection Handler. Please check the configuration attributes SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap destinations has been found. No trap will be sent SEVERE_ERR_ASN1_READ_ERROR_1500=An error occured while accessing the underlying data source: %s SEVERE_ERR_ASN1_EOF_ERROR_1501=An unexpected end of file reached while trying to read %d bytes from the underlying data source SEVERE_ERR_ASN1_INVALID_STATE_1502=Invalid reader state: %d SEVERE_ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503=Cannot decode the provided subtree delete control because it contains a value ###SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF \ ### connection handler was processing LDIF file %s: %s ###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the \ ### LDIF connection handler was attempting to rename partially-processed file \ ### from %s to %s: %s ###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the \ ### LDIF connection handler was attempting to delete processed file %s: %s ###SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use INFO_SNMP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_1458=Port SNMP sur lequel le gestionnaire de connexion accepte les demandes SNMP. Les modifications apport\u00e9es \u00e0 cet attribut de configuration ne seront effectives qu'apr\u00e8s la d\u00e9sactivation et la r\u00e9activation du gestionnaire de connexion, ou qu'apr\u00e8s le red\u00e9marrage de Directory Server ###SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined \ ### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ ### required attribute ###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected \ ### error occurred while processing the ds-cfg-listen-port attribute in \ ### configuration entry %s, which is used to specify the port on which to listen \ ### for client connections: %s ###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected \ ### error occurred when this connection handler started ###SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined \ ### for this connection handler. The configuration parameters ds-cfg-listen-port \ ### and ds-cfg-trap-port are required by the connection handler to start ###SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is \ ### an unknown host. Traps will not be sent to this destination ###SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the \ ### appropriate OpenDMK jar files to enable the SNMP Connection Handler. \ ### Please go under http://opendmk.dev.java.net and set the \ ### opendmk-jarfile configuration parameter to set the full path \ ### of the required jdmkrt.jar file. The SNMP connection Handler didn't started ###SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=Cannot initialize the \ ### SNMP Connection Handler. Please check the configuration attributes ###SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap \ ### destinations has been found. No trap will be sent ###SEVERE_ERR_ASN1_READ_ERROR_1500=An error occured while accessing the \ ### underlying data source: %s ###SEVERE_ERR_ASN1_EOF_ERROR_1501=An unexpected end of file reached while trying \ ### to read %d bytes from the underlying data source ###SEVERE_ERR_ASN1_INVALID_STATE_1502=Invalid reader state: %d ###SEVERE_ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503=Cannot decode the provided \ ### subtree delete control because it contains a value SEVERE_ERR_CONNHANDLER_SSL_CANNOT_INITIALIZE_1504=Une erreur s'est produite lors d'une tentative d'initialiser le contexte SSL \u00e0 utiliser dans le gestionnaire de connexion LDAP\u00a0: %s MILD_ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSION_1505=Directory Server ne prend pas en charge la version de protocole LDAP %d. Cette connexion va \u00eatre ferm\u00e9e SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506=The specified OpenDMK jar file '%s' could not be found. Verify that the value set in the opendmk-jarfile configuration parameter of the SNMP connection handler is the valid path to the jdmkrt.jar file and that the file is accessible SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507=The required classes could not be loaded using jar file '%s'. Verify that the jar file is not corrupted MILD_ERR_CANNOT_DECODE_CONTROL_VALUE_1508=Cannot decode the provided control %s because an error occurred while attempting to decode the control value: %s ###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506=The specified \ ### OpenDMK jar file '%s' could not be found. Verify that the value set in the \ ### opendmk-jarfile configuration parameter of the SNMP connection handler is the \ ### valid path to the jdmkrt.jar file and that the file is accessible ###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507=The required \ ### classes could not be loaded using jar file '%s'. Verify that the jar file \ ### is not corrupted MILD_ERR_CANNOT_DECODE_CONTROL_VALUE_1508=Impossible de d\u00e9coder le contr\u00f4le fourni %s, car une erreur s'est produite lors de la tentative de d\u00e9codage de sa valeur : %s MILD_ERR_ECLN_NO_CONTROL_VALUE_1509=Impossible de d\u00e9coder le contr\u00f4le de notification de journal de modifications d'entr\u00e9e fourni, car il ne poss\u00e8de pas de valeur MILD_ERR_ECLN_CANNOT_DECODE_VALUE_1510=Impossible de d\u00e9coder le contr\u00f4le de notification de journal de modifications d'entr\u00e9e fourni, car une erreur s'est produite lors de la tentative de d\u00e9codage de sa valeur : %s
