mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git
opendj-sdk/opends/src/messages/messages/extension_de.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=Beim Versuch, die base64-Verschl\u00fcsselung des Passwortwerts %s zu entschl\u00fcsseln, ist ein Fehler aufgetreten: %s MILD_ERR_PWSCHEME_NOT_REVERSIBLE_3=Das Speicherschema des Passworts %s ist nicht umkehrbar, daher ist es nicht m\u00f6glich, die Nur-Text-Version eines verschl\u00fcsselten Passworts wiederherzustellen MILD_ERR_JMX_ALERT_HANDLER_CANNOT_REGISTER_4=Beim Registrieren der JMX-Behandlungsroutine f\u00fcr Warnungen beim MBean-Server ist ein Fehler aufgetreten: %s MILD_ERR_PWSCHEME_CANNOT_ENCODE_PASSWORD_5=Beim Versuch, ein Passwort mithilfe des in Klasse %s definierten Speicherschemas zu verschl\u00fcsseln, ist ein unerwarteter Fehler aufgetreten: %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=Vorladen des Eintragscache f\u00fcr Backend %s wird gestartet NOTICE_CACHE_PRELOAD_PROGRESS_REPORT_11=Beim Vorladen des Eintragscache f\u00fcr Backend %s wurden %d Eintr\u00e4ge verarbeitet, %d MB freier Heap-Arbeitsspeicher verf\u00fcgbar NOTICE_CACHE_PRELOAD_PROGRESS_DONE_12=Vorladen des Eintragscache f\u00fcr Backend %s ist abgeschlossen; es wurden insgesamt %d Eintr\u00e4ge verarbeitet 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=Die Folge f\u00fcr die erweiterte Anforderung zur Passwort\u00e4nderung enthielt ein ASN.1-Element eines ung\u00fcltigen Typs: %s MILD_ERR_EXTOP_PASSMOD_CANNOT_DECODE_REQUEST_33=Beim Versuch, die Folge der erweiterten Anforderung zur Passwort\u00e4nderung zu entschl\u00fcsseln, ist ein unerwarteter Fehler aufgetreten: %s MILD_ERR_EXTOP_PASSMOD_NO_AUTH_OR_USERID_34=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da sie keine Autorisierungs-ID enth\u00e4lt und die zugrunde liegende Verbindung nicht authentifiziert ist 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=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da der Server "%s" nicht als g\u00fcltigen DN zur Verwendung in der Autorisierungs-ID des Vorgangs entschl\u00fcsseln konnte MILD_ERR_EXTOP_PASSMOD_INVALID_AUTHZID_STRING_37=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da sie ein ung\u00fcltiges userIdentity-Feld enthielt. Die angegebene userIdentity-Zeichenfolge lautete "%s" MILD_ERR_EXTOP_PASSMOD_NO_USER_ENTRY_BY_AUTHZID_38=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da es nicht m\u00f6glich ist, den zu aktualisierenden Benutzereintrag basierend auf dem Autorisierungs-DN "%s" zu identifizieren @@ -73,69 +85,171 @@ MILD_ERR_EXTOP_PASSMOD_MULTIPLE_ENTRIES_BY_AUTHZID_40=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da die angegebene Autorisierungs-UID "%s" mit mehreren Eintr\u00e4gen im Verzeichnis \u00fcbereinstimmt MILD_ERR_EXTOP_PASSMOD_INVALID_OLD_PASSWORD_41=Die erweiterte Anforderung zur Passwort\u00e4nderung kann nicht verarbeitet werden, da das derzeit f\u00fcr den Benutzer angegebene Passwort ung\u00fcltig ist INFO_FILE_KEYMANAGER_DESCRIPTION_FILE_43=Pfad zur Datei mit den Schl\u00fcsselspeicherinformationen f\u00fcr Directory-Server. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Schl\u00fcsselspeichertyp f\u00fcr den Directory-Server-Schl\u00fcsselspeicher. G\u00fcltige Werte m\u00fcssen immer 'JKS' und 'PKCS12' enthalten, unterschiedliche Implementierungen k\u00f6nnen jedoch auch andere Werte zulassen. Ist kein Wert angegeben, wird der JVM-Standardwert verwendet. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Name der Java-Eigenschaft, die die f\u00fcr den Zugriff auf den dateibasierten Schl\u00fcsselmanager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Name der Umgebungsvariablen, die die f\u00fcr den Zugriff auf den dateibasierten Schl\u00fcsselmanager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Pfad zu der Textdatei, deren einziger Inhalt eine einzelne Zeile mit der f\u00fcr den Zugriff auf den dateibasierten Schl\u00fcsselmanager ben\u00f6tigten Klartext-PIN sein sollte. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Der Wert des Attributs ds-cfg-key-store-file im Konfigurationseintrag %s wurde in %s aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft INFO_FILE_KEYMANAGER_UPDATED_TYPE_65=Der Wert des Attributs ds-cfg-key-store-type im Konfigurationseintrag %s wurde in %s aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft INFO_FILE_KEYMANAGER_UPDATED_PIN_66=Die f\u00fcr den Zugriff auf den dateibasierten Schl\u00fcsselmanager verwendete PIN wurde aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft INFO_PKCS11_KEYMANAGER_DESCRIPTION_PIN_PROPERTY_67=Name der Java-Eigenschaft, die die f\u00fcr den Zugriff auf den PKCS#11-Schl\u00fcsselmanager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Name der Umgebungsvariablen, die die f\u00fcr den Zugriff auf den PKCS#11-Schl\u00fcsselmanager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Pfad zu der Textdatei, deren einziger Inhalt eine einzelne Zeile mit der f\u00fcr den Zugriff auf den PKCS#11-Schl\u00fcsselmanager ben\u00f6tigten Klartext-PIN sein sollte. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=F\u00fcr den Zugriff auf den PKCS#11-Schl\u00fcsselmanager ben\u00f6tigte Klartext-PIN. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Die f\u00fcr den Zugriff auf den PKCS#11-Schl\u00fcsselmanager verwendete PIN wurde aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Schl\u00fcsselmanager in Kraft 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=Pfad zur Datei mit den Trust-Speicherinformationen f\u00fcr Directory-Server. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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=Schl\u00fcsselspeichertyp f\u00fcr den Directory-Server-Trust-Speicher. G\u00fcltige Werte m\u00fcssen immer 'JKS' und 'PKCS12' enthalten, unterschiedliche Implementierungen k\u00f6nnen jedoch auch andere Werte zulassen. Ist kein Wert angegeben, wird der JVM-Standardwert verwendet. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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=Name der Java-Eigenschaft, die die f\u00fcr den Zugriff auf den dateibasierten Trust-Manager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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 ###SEVERE_ERR_FILE_TRUSTMANAGER_PIN_PROPERTY_NOT_SET_92=Java property %s which \ ### is specified in attribute ds-cfg-trust-store-pin-property of configuration \ ### entry %s should contain the PIN needed to access the file-based trust \ ### manager, but this property is not set ###SEVERE_ERR_FILE_TRUSTMANAGER_CANNOT_DETERMINE_PIN_PROPERTY_93=An unexpected \ ### error occurred while trying to determine the value of configuration attribute \ ### ds-cfg-trust-store-pin-property in configuration entry %s: %s INFO_FILE_TRUSTMANAGER_DESCRIPTION_PIN_ENVAR_94=Name der Umgebungsvariablen, die die f\u00fcr den Zugriff auf den dateibasierten Trust-Manager ben\u00f6tigte Klartext-PIN enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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_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=Pfad zu der Textdatei, deren einziger Inhalt eine einzelne Zeile mit der f\u00fcr den Zugriff auf den dateibasierten Trust-Manager ben\u00f6tigten Klartext-PIN sein sollte. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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=F\u00fcr den Zugriff auf den dateibasierten Trust-Manager ben\u00f6tigte Klartext-PIN. \u00c4nderungen an diesem Konfigurationsattribut treten beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft 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=Der Wert des Attributs ds-cfg-trust-store-file im Konfigurationseintrag %s wurde in %s aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft INFO_FILE_TRUSTMANAGER_UPDATED_TYPE_108=Der Wert des Attributs ds-cfg-trust-store-type im Konfigurationseintrag %s wurde in %s aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft INFO_FILE_TRUSTMANAGER_UPDATED_PIN_109=Die f\u00fcr den Zugriff auf den dateibasierten Trust-Manager verwendete PIN wurde aktualisiert. Der neue Wert tritt beim n\u00e4chsten Zugriff auf den Trust-Manager in Kraft @@ -153,21 +267,41 @@ MILD_ERR_STARTTLS_NOT_TLS_CAPABLE_129=StartTLS kann unter dieser Client-Verbindung nicht verwendet werden, da dieser Verbindungstyp die Verwendung von StartTLS zum Schutz der Kommunikation nicht erm\u00f6glicht MILD_ERR_STARTTLS_ERROR_ON_ENABLE_130=Beim Versuch, den Manager f\u00fcr die Sicherheit der TLS-Verbindung in der Client-Verbindung f\u00fcr StartTLS zu aktivieren, ist ein unerwarteter Fehler aufgetreten: %s INFO_SASLEXTERNAL_DESCRIPTION_VALIDATION_POLICY_131=Gibt an, ob die Behandlungsroutine f\u00fcr den SASL EXTERNAL-Mechanismus versuchen soll, das Peer-Zertifikat anhand eines Zertifikats im Eintrag des entsprechenden Benutzers zu validieren. Folgende Werte sind m\u00f6glich: "true" (es wird immer versucht, das Zertifikat zu validieren, und wenn keine Zertifikate vorhanden sind, wird ein Fehler generiert, ), "false" (es wird nie versucht, das Peer-Zertifikat zu validieren) oder "ifpresent" (das Peer-Zertifikat wird validiert, wenn der Benutzereintrag mindestens ein Zertifikat enth\u00e4lt, wenn der Eintrag keine Zertifikate enth\u00e4lt, wird jedoch kein Fehler generiert). \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###SEVERE_ERR_SASLEXTERNAL_INVALID_VALIDATION_VALUE_132=Configuration entry %s \ ### has an invalid value %s for attribute \ ### ds-cfg-certificate-validation-policy. The value must be one of \ ### "always", "never", or "ifpresent" ###SEVERE_ERR_SASLEXTERNAL_CANNOT_GET_VALIDATION_POLICY_133=An unexpected error \ ### occurred while attempting to determine the value of the \ ### ds-cfg-certificate-validation-policy attribute in configuration entry \ ### %s: %s INFO_SASLEXTERNAL_DESCRIPTION_CERTIFICATE_ATTRIBUTE_134=Name des Attributs, das die Zertifikatinformationen in Benutzereintr\u00e4gen zu Validierungszwecken enthalten wird. Es muss der Name eines g\u00fcltigen Attributtyps angegeben werden, der im Serverschema definiert ist. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Die Authentifizierung \u00fcber SASL EXTERNAL ist nicht m\u00f6glich, da der zugeordnete Benutzereintrag %s keine Zertifikate aufweist, mit denen das vorgelegte Peer-Zertifikat verifiziert werden kann MILD_ERR_SASLEXTERNAL_PEER_CERT_NOT_FOUND_138=Die Authentifizierung \u00fcber SASL EXTERNAL ist nicht m\u00f6glich, da der zugeordnete Benutzereintrag %s nicht das vom Client vorgelegte Peer-Zertifikat enthielt MILD_ERR_SASLEXTERNAL_CANNOT_VALIDATE_CERT_139=Beim Versuch, das vom Client vorgelegte Peer-Zertifikat mit einem Zertifikat aus dem Benutzereintrag %s zu validieren, ist ein Fehler aufgetreten: %s INFO_SASLEXTERNAL_UPDATED_VALIDATION_POLICY_140=Das Attribut ds-cfg-certificate-validation-policy im Konfigurationseintrag %s wurde aktualisiert. Die neue Zertifikatvalidierungsrichtlinie f\u00fcr den Client ist %s INFO_SASLEXTERNAL_UPDATED_CERT_ATTR_141=Das Attribut ds-cfg-certificate-attribute im Konfigurationseintrag %s wurde aktualisiert. Bei der Validierung von Peer-Zertifikaten wird jetzt das Attribut %s verwendet INFO_SASLPLAIN_DESCRIPTION_USERNAME_ATTRIBUTE_142=Name des Attributs, mit dem Benutzereintr\u00e4ge basierend auf der w\u00e4hrend der SASL PLAIN-Authentifizierung angegebenen authcID/authzID identifiziert werden. Es muss der Name eines g\u00fcltigen Attributtyps angegeben werden, der im Serverschema definiert ist. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Basis-DN, der bei der Suche nach Eintr\u00e4gen basierend auf der w\u00e4hrend der SASL PLAIN-Authentifizierung angegebenen authcID/authzID zu verwenden ist. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Bei einer SASL PLAIN-Authentifizierung m\u00fcssen SASL-Berechtigungsnachweise angegeben werden, die Verbindungsanforderung enthielt jedoch keine MILD_ERR_SASLPLAIN_NO_NULLS_IN_CREDENTIALS_148=Die SASL PLAIN-Verbindungsanforderung enthielt keine NULL-Zeichen. Autorisierungs-ID und Authentifizierungs-ID sowie Authentifizierungs-ID und Passwort m\u00fcssen jeweils durch NULL-Zeichen getrennt sein MILD_ERR_SASLPLAIN_NO_SECOND_NULL_149=Die Berechtigungsnachweise in der SASL PLAIN-Verbindungsanforderung enthielten kein zweites NULL-Zeichen, das als Trennzeichen zwischen der Authentifizierungs-ID und dem Passwort erforderlich ist @@ -187,12 +321,22 @@ INFO_SASLPLAIN_CANNOT_LOCK_ENTRY_163=Der Directory-Server konnte f\u00fcr den Benutzereintrag %s keine Lesesperre erhalten, um ihn abrufen zu k\u00f6nnen MILD_ERR_SEDCM_CANNOT_LOCK_ENTRY_164=Der Directory-Server konnte f\u00fcr den Benutzereintrag %s keine Lesesperre erhalten, um ihn abrufen zu k\u00f6nnen INFO_SASLANONYMOUS_TRACE_165=Der SASL ANONYMOUS-Verbindungsvorgang (conn=%d, op=%d) hat Verfolgungsinformationen ergeben: %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 ###SEVERE_ERR_SASLCRAMMD5_CANNOT_GET_MESSAGE_DIGEST_166=An unexpected error \ ### occurred while attempting to obtain an MD5 digest engine for use by the \ ### CRAM-MD5 SASL handler: %s INFO_SASLCRAMMD5_DESCRIPTION_USERNAME_ATTRIBUTE_167=Name des Attributs, mit dem Benutzereintr\u00e4ge basierend auf dem w\u00e4hrend der SASL CRAM-MD5-Authentifizierung angegebenen Benutzernamen identifiziert werden. Es muss der Name eines g\u00fcltigen Attributtyps angegeben werden, der im Serverschema definiert ist. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Basis-DN, der bei der Suche nach Eintr\u00e4gen basierend auf dem w\u00e4hrend der SASL CRAM-MD5-Authentifizierung angegebenen Benutzernamen zu verwenden ist. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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_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=Die Verbindungsanforderung SASL CRAM-MD5 enthielt SASL-Berechtigungsnachweise, f\u00fcr diese Client-Verbindung ist jedoch keine Abfrage gespeichert. Die erste CRAM-MD5-Verbindungsanforderung in dem zweistufigen Prozess darf keine Client-SASL-Berechtigungsnachweise beinhalten MILD_ERR_SASLCRAMMD5_INVALID_STORED_CHALLENGE_173=Die Verbindungsanforderung SASL CRAM-MD5 enthielt SASL-Berechtigungsnachweise, die f\u00fcr diese Client-Verbindung gespeicherten SASL-Statusinformationen weisen jedoch nicht das korrekte Format f\u00fcr die Abfrage auf MILD_ERR_SASLCRAMMD5_NO_SPACE_IN_CREDENTIALS_174=Die Verbindungsanforderung SASL CRAM-MD5 vom Client enthielt SASL-Berechtigungsnachweise, Benutzername und Authentifizierungsverarbeitung waren jedoch nicht durch ein Leerzeichen getrennt @@ -215,7 +359,9 @@ INFO_SASLCRAMMD5_UPDATED_USER_BASE_DN_191=Das Attribut ds-cfg-user-base-dn im Konfigurationseintrag %s wurde aktualisiert. Der DN %s wird nun beim Nachschlagen von Benutzereintr\u00e4gen basierend auf ihrem Benutzernamen als Grundlage f\u00fcr die Suche verwendet INFO_SASL_UNSUPPORTED_CALLBACK_192=F\u00fcr den SASL-Server wurde ein unerwarteter R\u00fcckruf zur Verwendung bei der %s-Authentifizierung angegeben: %s MILD_ERR_SASL_NO_CREDENTIALS_193=Die Client-Verbindung wies %s-Statusinformationen auf, die darauf hinweisen, dass der Client im Begriff war, eine %s-Verbindung herzustellen, die Verbindungsanforderung jedoch keine Berechtigungsnachweise enthielt 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=Beim Versuch, einen %s-Kontext zu erstellen, ist ein unerwarteter Fehler aufgetreten: %s MILD_ERR_SASL_CANNOT_DECODE_USERNAME_AS_DN_196=Beim Versuch, den SASL-%s-Benutzernamen %s zu entschl\u00fcsseln, ist ein Fehler aufgetreten, da er offenbar einen DN enthielt, die DN-Entschl\u00fcsselung jedoch fehlgeschlagen ist: %s MILD_ERR_SASL_USERNAME_IS_NULL_DN_197=Bei dem Benutzernamen in der Verbindungsanforderung SASL %s handelt es sich offenbar um einen leeren DN. Dies ist nicht zul\u00e4ssig @@ -230,20 +376,25 @@ MILD_ERR_SASL_CANNOT_MAP_AUTHZID_206=Beim Versuch, die Autorisierungs-ID %s einem Benutzereintrag zuzuordnen, ist ein Fehler aufgetreten: %s MILD_ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDS_207=Beim Versuch, die Klartextpassw\u00f6rter f\u00fcr Benutzer %s zwecks Durchf\u00fchrung der SASL %s-Authentifizierung abzurufen, ist ein Fehler aufgetreten: %s MILD_ERR_SASL_NO_REVERSIBLE_PASSWORDS_208=Die Authentifizierung mit SASL %s ist f\u00fcr Benutzer %s nicht m\u00f6glich, da keines der Passw\u00f6rter im Benutzereintrag in umkehrbarer Form gespeichert ist 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=Der Authentifizierungsbenutzer %s verf\u00fcgt nicht \u00fcber die zum Annehmen einer anderen Autorisierungsidentit\u00e4t erforderlichen Berechtigungen MILD_ERR_SASL_AUTHZID_INSUFFICIENT_ACCESS_211=Der Authentifizierungsbenutzer %s verf\u00fcgt nicht \u00fcber die zum Annehmen einer anderen Autorisierungsidentit\u00e4t erforderlichen Berechtigungen MILD_ERR_SASL_AUTHENTRY_NO_MAPPED_ENTRY_212=Der Server konnte keinen Eintrag finden, der der Autorisierungs-ID %s entspricht. 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=Beim Versuch, die Autorisierungs-ID %s einem Benutzereintrag zuzuordnen, ist ein Fehler aufgetreten: %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=Beim Versuch, den JAAS-Anmeldekontext f\u00fcr die GSSAPI-Authentifizierung zu erstellen, ist ein Fehler aufgetreten: %s MILD_ERR_SASLGSSAPI_NO_CLIENT_CONNECTION_217=Es war keine Client-Verbindung zur Verwendung f\u00fcr die Verarbeitung der GSSAPI-Verbindungsanforderung verf\u00fcgbar INFO_GSSAPI_PRINCIPAL_NAME_218=GSSAPI-Mechanismus, der folgenden Principal-Namen verwendet: %s INFO_GSSAPI_SERVER_FQDN_219=GSSAPI SASL-Mechanismus, der den vollst\u00e4ndigen Server-Dom\u00e4nennamen mit %s verwendet INFO_DIGEST_MD5_REALM_220=DIGEST-MD5 SASL-Mechanismus, der folgenden Bereich verwendet: %s INFO_DIGEST_MD5_SERVER_FQDN_221=DIGEST-MD5 SASL-Mechanismus, der den vollst\u00e4ndigen Server-Dom\u00e4nennamen mit %s verwendet SEVERE_ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES_277=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um die angen\u00e4herte Autorisierungssteuerung zu verwenden ###SEVERE_ERR_EXTOP_WHOAMI_PROXYAUTH_INSUFFICIENT_PRIVILEGES_277=You do not have \ ### sufficient privileges to use the proxied authorization control INFO_EXACTMAP_DESCRIPTION_MATCH_ATTR_298=Name oder OID des Attributs, dessen Wert genau mit der f\u00fcr diese Identit\u00e4tszuordnung angegebenen ID-Zeichenfolge \u00fcbereinstimmen soll. Es muss mindestens ein Wert angegeben werden. Alle Werte m\u00fcssen auf den Namen oder die OID eines im Directory-Server-Schema definierten Attributtyps verweisen. Wenn mehrere Attributtypen oder OIDs angegeben sind, muss mindestens eines dieser Attribute den angegebenen Wert der ID-Zeichenfolge in genau einem Eintrag enthalten MILD_ERR_EXACTMAP_NO_MATCH_ATTR_299=Der Konfigurationseintrag %s weist keine Werte f\u00fcr das Attribut ds-cfg-match-attribute auf, mit dem angegeben wird, mithilfe welcher Attribute eine bestimmte ID-Zeichenfolge einem Benutzereintrag zugeordnet werden kann MILD_ERR_EXACTMAP_UNKNOWN_ATTR_300=Der Konfigurationseintrag %s enth\u00e4lt f\u00fcr das Attribut cfg-match-attribute den Wert %s, hierbei handelt es sich jedoch nicht um einen g\u00fcltigen Namen oder eine g\u00fcltige OID f\u00fcr einen im Directory-Server-Schema definierten Attributtyp @@ -320,11 +471,6 @@ MILD_ERR_ERRORLOG_ACCTNOTHANDLER_INVALID_TYPE_373=Der Konfigurationseintrag %s enth\u00e4lt den unbekannten Benachrichtigungstyp f\u00fcr den Kontostatus %s MILD_ERR_ERRORLOG_ACCTNOTHANDLER_CANNOT_GET_NOTIFICATION_TYPES_374=Beim Versuch, die Benachrichtigungstypen f\u00fcr den Kontostatus aus Konfigurationseintrag %s zu bestimmen, ist ein Fehler aufgetreten: %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=Beim Versuch, die Klartextpassw\u00f6rter f\u00fcr Benutzer %s zwecks Durchf\u00fchrung der SASL CRAM-MD5-Authentifizierung abzurufen, ist ein Fehler aufgetreten: %s MILD_ERR_SASLPLAIN_CANNOT_CHECK_PASSWORD_VALIDITY_378=Beim Versuch, das Passwort f\u00fcr den Benutzer %s w\u00e4hrend der SASL PLAIN-Authentifizierung zu verifizieren, ist ein Fehler aufgetreten: %s MILD_ERR_STARTTLS_ERROR_SENDING_CLEAR_RESPONSE_379=Beim Versuch, nach dem Beginn der TLS-Aushandlung die Klartextantwort an den Client zu senden, ist ein Fehler aufgetreten: %s @@ -341,23 +487,12 @@ MILD_ERR_STATICGROUP_ADD_MEMBER_UPDATE_FAILED_390=Benutzer %s kann nicht als neues Mitglied der statischen Gruppe %s hinzugef\u00fcgt werden, da beim Versuch, eine interne \u00c4nderung zur Aktualisierung der Gruppe durchzuf\u00fchren, ein Fehler aufgetreten ist: %s MILD_ERR_STATICGROUP_REMOVE_MEMBER_UPDATE_FAILED_391=Benutzer %s kann nicht als Mitglied der statischen Gruppe %s entfernt werden, da beim Versuch, eine interne \u00c4nderung zur Aktualisierung der Gruppe durchzuf\u00fchren, ein Fehler aufgetreten ist: %s MILD_ERR_EXTOP_PASSMOD_INSUFFICIENT_PRIVILEGES_392=Sie verf\u00fcgen nicht \u00fcber die zum Zur\u00fccksetzen von Passw\u00f6rtern erforderlichen Berechtigungen MILD_ERR_SASLDIGESTMD5_EMPTY_AUTHZID_393=Die angegebene Autorisierungs-ID war leer, was bei der DIGEST-MD5-Authentifizierung nicht zul\u00e4ssig ist MILD_ERR_SASLDIGESTMD5_AUTHZID_INVALID_DN_394=Die angegebene Autorisierungs-ID %s enthielt einen ung\u00fcltigen DN: %s MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_SUCH_ENTRY_396=Der als Autorisierungsidentit\u00e4t angegebene Eintrag %s existiert nicht MILD_ERR_SASLDIGESTMD5_AUTHZID_CANNOT_GET_ENTRY_397=Der als Autorisierungsidentit\u00e4t angegebene Eintrag %s konnte nicht abgerufen werden: %s MILD_ERR_SASLDIGESTMD5_AUTHZID_NO_MAPPED_ENTRY_398=Der Server konnte keinen Eintrag finden, der der Autorisierungs-ID %s entspricht MILD_ERR_SASLDIGESTMD5_CANNOT_MAP_AUTHZID_399=Beim Versuch, die Autorisierungs-ID %s einem Benutzereintrag zuzuordnen, ist ein Fehler aufgetreten: %s MILD_ERR_SASLPLAIN_AUTHZID_INVALID_DN_400=Die angegebene Autorisierungs-ID %s enthielt einen ung\u00fcltigen DN: %s MILD_ERR_SASLPLAIN_AUTHZID_INSUFFICIENT_PRIVILEGES_401=Der Authentifizierungsbenutzer %s verf\u00fcgt nicht \u00fcber die zum Angeben einer alternativen Autorisierungs-ID ben\u00f6tigten Berechtigungen MILD_ERR_SASLPLAIN_AUTHZID_NO_SUCH_ENTRY_402=Der dem Autorisierungs-DN %s entsprechende Eintrag ist in Directory-Server nicht vorhanden @@ -370,47 +505,94 @@ MILD_ERR_SASLEXTERNAL_CANNOT_GET_CERT_MAPPER_DN_409=Beim Versuch, den Zertifikatszuordnungs-DN aus dem Konfigurationseintrag %s abzurufen, ist ein Fehler aufgetreten: %s INFO_SASLEXTERNAL_UPDATED_CERT_MAPPER_DN_410=Das Attribut ds-cfg-certificate-mapper im Konfigurationseintrag %s wurde aktualisiert. Die Zertifikatszuordnung %s wird nun zum Zuordnen von Zertifikaten zu Benutzereintr\u00e4gen verwendet INFO_SDTUACM_DESCRIPTION_SUBJECT_ATTR_411=Name des Attributtyps in Benutzereintr\u00e4gen, der die Betreffs der Zertifikate des Benutzers enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Basis-DNs, unter denen die Suche nach \u00fcbereinstimmenden Benutzereintr\u00e4gen durchgef\u00fchrt wird. Sind keine Basis-DNs angegeben, sucht der Server unter allen \u00f6ffentlichen Namenskontexten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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=Die angegebene Zertifikatkette konnte keinem Benutzereintrag zugeordnet werden, da kein Peer-Zertifikat verf\u00fcgbar war SEVERE_ERR_SDTUACM_PEER_CERT_NOT_X509_418=Die angegebene Zertifikatkette konnte keinem Benutzer zugeordnet werden, da es sich bei dem Peer-Zertifikat nicht um ein X.509-Zertifikat handelte. (Das Format des Peer-Zertifikats war %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 ###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=Name des Attributtyps in Benutzereintr\u00e4gen, mit dem die Zuordnung zwischen Attributen in Zertifikatsbetreffs und Attributen in Benutzereintr\u00e4gen definiert wird. Die Werte m\u00fcssen das Format 'certattr:userattr' aufweisen. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Basis-DNs, unter denen die Suche nach \u00fcbereinstimmenden Benutzereintr\u00e4gen durchgef\u00fchrt wird. Sind keine Basis-DNs angegeben, sucht der Server unter allen \u00f6ffentlichen Namenskontexten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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=Die angegebene Zertifikatkette konnte keinem Benutzereintrag zugeordnet werden, da kein Peer-Zertifikat verf\u00fcgbar war SEVERE_ERR_SATUACM_PEER_CERT_NOT_X509_430=Die angegebene Zertifikatkette konnte keinem Benutzer zugeordnet werden, da es sich bei dem Peer-Zertifikat nicht um ein X.509-Zertifikat handelte. (Das Format des Peer-Zertifikats war %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 ###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=Name des Attributtyps in Benutzereintr\u00e4gen, der die Fingerabdr\u00fccke der Zertifikate des Benutzers enth\u00e4lt. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###SEVERE_ERR_FCM_NO_FINGERPRINT_ATTR_435=Configuration entry %s does not \ ### contain required attribute %s, which is used to specify which attribute \ ### should contain the fingerprints of the certificates held by users ###SEVERE_ERR_FCM_NO_SUCH_ATTR_436=Configuration entry %s indicates that \ ### certificate fingerprints should be held in attribute %s, but this attribute \ ### is not defined in the server schema ###SEVERE_ERR_FCM_CANNOT_GET_FINGERPRINT_ATTR_437=An error occurred while \ ### attempting to determine which attribute type should be used to hold \ ### certificate fingerprints from configuration entry %s: %s INFO_FCM_DESCRIPTION_FINGERPRINT_ALGORITHM_438=Name des Verarbeitungsalgorithmus, der f\u00fcr die Zertifikatfingerabdr\u00fccke verwendet wird. Der Wert muss entweder 'MD5' oder 'SHA1' lauten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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 ###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=Basis-DNs, unter denen die Suche nach \u00fcbereinstimmenden Benutzereintr\u00e4gen durchgef\u00fchrt wird. Sind keine Basis-DNs angegeben, sucht der Server unter allen \u00f6ffentlichen Namenskontexten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft 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=Die angegebene Zertifikatkette konnte keinem Benutzereintrag zugeordnet werden, da kein Peer-Zertifikat verf\u00fcgbar war SEVERE_ERR_FCM_PEER_CERT_NOT_X509_444=Die angegebene Zertifikatkette konnte keinem Benutzer zugeordnet werden, da es sich bei dem Peer-Zertifikat nicht um ein X.509-Zertifikat handelte. (Das Format des Peer-Zertifikats war %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 ###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=Wert "%s" in Eintrag "%s" kann nicht als LDAP-URL entschl\u00fcsselt werden: %s MILD_ERR_DYNAMICGROUP_NESTING_NOT_SUPPORTED_448=Dynamische Gruppen unterst\u00fctzen keine geschachtelten Gruppen MILD_ERR_DYNAMICGROUP_ALTERING_MEMBERS_NOT_SUPPORTED_449=Dynamische Gruppen unterst\u00fctzen keine expliziten \u00c4nderungen der Mitgliedschaft MILD_WARN_DYNAMICGROUP_NONEXISTENT_BASE_DN_450=Der in der dynamischen Gruppe %2$s angegebene Basis-DN %1$s ist auf dem Server nicht vorhanden 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 ###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=Unterschiede, die ein Passwort mindestens aufweisen muss. Ist der Wert null, gibt es keine mindestens erforderlichen Unterschiede. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft MILD_ERR_PWDIFFERENCEVALIDATOR_CANNOT_DETERMINE_MIN_DIFFERENCE_454=Beim Versuch, die mindestens erforderlichen Passwortunterschiede anhand des Attributs ds-cfg-min-password-difference zu bestimmen, ist ein Fehler aufgetreten: %s INFO_PWDIFFERENCEVALIDATOR_UPDATED_MIN_DIFFERENCE_455=Die mindestens erforderlichen Passwortunterschiede wurden in %d ge\u00e4ndert @@ -437,53 +619,127 @@ MILD_ERR_VIRTUAL_STATIC_GROUP_TARGET_CANNOT_BE_VIRTUAL_476=Die virtuelle statische Gruppe %s verweist auf die Zielgruppe %s, die selbst eine virtuelle statische Gruppe ist. Eine virtuelle statische Gruppe darf nicht auf eine andere virtuelle statische Gruppe als Zielgruppe verweisen NOTICE_FSCACHE_RESTORE_484=Wiederherstellung des best\u00e4ndigen Eintragscache-Status wird gespeichert, dies kann einige Zeit in Anspruch nehmen NOTICE_FSCACHE_SAVE_485=Der Status des Eintragscache wird als best\u00e4ndig festgelegt, dies kann einige Zeit in Anspruch nehmen 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=%d best\u00e4ndige Cache-Eintr\u00e4ge in Eintragscache wiederhergestellt NOTICE_FSCACHE_SAVE_REPORT_498=%d Cache-Eintr\u00e4ge als best\u00e4ndig festgelegt NOTICE_FSCACHE_INDEX_NOT_FOUND_499=Es wurde kein vorheriger Status f\u00fcr best\u00e4ndigen Cache gefunden. Es wird ein leerer Cache verwendet 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=Das Attribut %s kann nicht durchsucht werden und darf nicht in ansonsten nicht indizierten Suchfiltern enthalten sein 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. Zul\u00e4ssige Werte sind 'true' oder '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. Zul\u00e4ssige Werte sind 'true' oder '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=Beim Versuch, die Statusinformationen zur Passwortrichtlinie f\u00fcr Benutzer %s im Rahmen einer erweiterten Passwort\u00e4nderung zu aktualisieren, ist ein Fehler aufgetreten (Ergebniscode='%s', Fehlermeldung='%s') MILD_ERR_SASLDIGESTMD5_INVALID_DIGEST_URI_529=Die vom Client angegebenen DIGEST-MD5-Berechtigungsnachweise haben den ung\u00fcltigen Verarbeitungs-URI %s angefordert. Der erwartete Verarbeitungs-URI ist %s MILD_ERR_EXTOP_PASSMOD_PW_IN_HISTORY_530=Das angegebene neue Passwort ist bereits im Passwortverlauf enthalten MILD_ERR_SMTPALERTHANDLER_NO_SMTP_SERVERS_531=Directory-Server ist nicht f\u00fcr SMTP-Server konfiguriert. Die SMTP-Behandlungsroutine f\u00fcr Warnungen kann nur verwendet werden, wenn Directory-Server mit Informationen zu mindestens einem SMTP-Server konfiguriert ist 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=Das angegebene \u00dcbereinstimmungsmuster "%s" konnte nicht als regul\u00e4rer Ausdruck analysiert werden: %s MILD_ERR_REGEXMAP_UNKNOWN_ATTR_534=Der Konfigurationseintrag %s enth\u00e4lt f\u00fcr das Attribut cfg-match-attribute den Wert %s, hierbei handelt es sich jedoch nicht um einen g\u00fcltigen Namen oder eine g\u00fcltige OID f\u00fcr einen im Directory-Server-Schema definierten Attributtyp MILD_ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_535=Die verarbeitete ID-Zeichenfolge %s ist mehreren Benutzern zugeordnet @@ -509,21 +765,36 @@ MILD_ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKEN_555=In Spalte %2$d von Zeile %3$d wurde ein unbekanntes Token %1$s gefunden MILD_ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSE_556=Beim Versuch, die Nachrichtenvorlagendatei '%s' zu analysieren, auf die der Konfigurationseintrag '%s' verweist, ist ein Fehler aufgetreten: %s INFO_SMTP_ASNH_DEFAULT_SUBJECT_557=Benachrichtigung \u00fcber Status des Verzeichniskontos 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=Der angegebene erweiterte Vorgang f\u00fcr den symmetrischen Schl\u00fcssel kann nicht entschl\u00fcsselt werden, da er keinen Wert aufweist MILD_ERR_GET_SYMMETRIC_KEY_INVALID_TYPE_562=Der angegebene erweiterte Vorgang f\u00fcr den symmetrischen Schl\u00fcssel kann nicht entschl\u00fcsselt werden, da die Wertfolge ein Element mit dem ung\u00fcltigen Typ %s aufweist MILD_ERR_GET_SYMMETRIC_KEY_ASN1_DECODE_EXCEPTION_563=Erweiterte Anforderung f\u00fcr symmetrischen Schl\u00fcssel kann nicht entschl\u00fcsselt werden: %s MILD_ERR_GET_SYMMETRIC_KEY_DECODE_EXCEPTION_564=Beim Versuch, die Folge der erweiterten Anforderung f\u00fcr den symmetrischen Schl\u00fcssel zu entschl\u00fcsseln, ist ein unerwarteter Fehler aufgetreten: %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=Erweiterung geladen von Datei '%s' (Build %s, Revision %s) SEVERE_ERR_SASL_CREATE_SASL_SERVER_FAILED_572=Failed to create a SASL server for SASL mechanism %s using a server FQDN of %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=Die Initialisierung des GSSAPI SASL-Mechanismus-Handlers war efolgreich. INFO_GSSAPI_STOPPED_575=Der GSSAPI SASL-Mechanismus-Handler wurde angehalten.
