external-software/github_OpenIdentityPlatform_OpenDJ.git

			@@ -7,9 +7,9 @@
			tag.replication.synopsis=Replikation
			tag.security.synopsis=Authentication and authorization
			tag.user-management.synopsis=User management
			relation.access-control-handler.user-friendly-name=Access Control Handler
			relation.access-control-handler.synopsis=Access Control Handlers manage the application-wide access control. The OpenDS access control handler is defined through an extensible interface, so that alternate implementations can be created. Only one access control handler may be active in the server at any given time.
			relation.access-control-handler.description=Note that OpenDS also has a privilege subsystem, which may have an impact on what clients may be allowed to do in the server. For example, any user with the bypass-acl privilege is not subject to access control checking regardless of whether the access control implementation is enabled.
			relation.access-control-handler.user-friendly-name=Zugriffskontroll-Handler (Access Control Handler)
			relation.access-control-handler.synopsis=Access Control Handlers haben die applikationsweite Zugriffskontrolle inne. Der OpenDS Access Control Handler is durch ein erweiterbares Interface definiert um alternative Implementierungen zu erm\u00f6glichen. In einem Server kann zur gleichen zeit nur ein Access Control Handlers aktiviert sein.
			relation.access-control-handler.description=Beachten sie dass OpenDS auch ein Priviliegiensubsystem hat, welches u.a. auch bestimmt was Client Connections in dem Server ausf\u00fchren d\u00fcrfen oder nicht. Zum Beispiel wird jeder User der das bypass-acl Privileg innehat von der Acces Control Implementierung ignoriert.
			relation.account-status-notification-handler.user-friendly-name=Account Status Notification Handler
			relation.account-status-notification-handler.user-friendly-plural-name=Account Status Notification Handlers
			relation.account-status-notification-handler.synopsis=Account Status Notification Handlers are invoked to provide notification to users in some form (for example, by an email message) when the status of a user's account has changed in some way. The Account Status Notification Handler can be used to notify the user and/or administrators of the change.
			@@ -32,8 +32,8 @@
			relation.connection-handler.user-friendly-name=Connection Handler
			relation.connection-handler.user-friendly-plural-name=Verbindungs-Handler
			relation.connection-handler.synopsis=Connection Handlers are responsible for handling all interaction with the clients, including accepting the connections, reading requests, and sending responses.
			relation.crypto-manager.user-friendly-name=Crypto Manager
			relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations.
			relation.crypto-manager.user-friendly-name=Krypto-Manager
			relation.crypto-manager.synopsis=Der Krypto-Manager stellt ein allgemeines Interface bereit, das f\u00fcr Kompression, Dekompression, Hashing, Verschl\u00fcsselung und andere Arten von Kryptographischen Operationen geeignet ist.
			relation.entry-cache.user-friendly-name=Entry Cache
			relation.entry-cache.user-friendly-plural-name=Entry Caches
			relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve Directory Server performance.
			@@ -46,10 +46,10 @@
			relation.extension.description=It is an entry point for extensions that requires configuration objects that does not inherit from an existing top-level object.
			relation.global-configuration.user-friendly-name=Global Configuration
			relation.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDS Directory Server .
			relation.group-implementation.user-friendly-name=Group Implementation
			relation.group-implementation.user-friendly-plural-name=Group Implementations
			relation.group-implementation.synopsis=Group Implementations define named collections of users.
			relation.group-implementation.description=Different group implementations may have different ways of determining membership. For example, some groups may explicitly list the members, and/or they may dynamically determine membership.
			relation.group-implementation.user-friendly-name=Gruppenimplementierung
			relation.group-implementation.user-friendly-plural-name=Gruppenimplementierungen
			relation.group-implementation.synopsis=Gruppenimplementierungen definieren Namenssammlungen von Usern.
			relation.group-implementation.description=Verschiedene Gruppenimplementierungen stellen anhand von verschiedenen Arten die Gruppenmitgliedschaft fest. Zum Beispiel listen manche Gruppen die Mitglieder explizit und oder k\u00f6nnen die Mitgliedschaft dynamisch errechnen.
			relation.identity-mapper.user-friendly-name=Identity Mapper
			relation.identity-mapper.user-friendly-plural-name=Identity Mappers
			relation.identity-mapper.synopsis=Identity Mappers are responsible for establishing a mapping between an identifier string provided by a client, and the entry for the user that corresponds to that identifier. Identity Mappers are used to process several SASL mechanisms to map an authorization ID (e.g., a Kerberos principal when using GSSAPI) to a directory user. They are also used when processing requests with the proxied authorization control.
			@@ -66,10 +66,10 @@
			relation.log-rotation-policy.user-friendly-name=Log Rotation Policy
			relation.log-rotation-policy.user-friendly-plural-name=Log Rotation Policies
			relation.log-rotation-policy.synopsis=Log Rotation Policies are used to specify when log files should be rotated.
			relation.matching-rule.user-friendly-name=Matching Rule
			relation.matching-rule.user-friendly-plural-name=Matching Rules
			relation.matching-rule.synopsis=Matching Rules define a set of rules for performing matching operations against assertion values.
			relation.matching-rule.description=Matching rules are frequently associated with an attribute syntax and are used to compare values according to that syntax. For example, the distinguishedNameEqualityMatch matching rule can be used to determine whether two DNs are equal and can ignore unnecessary spaces around commas and equal signs, differences in capitalization in attribute names, an so on.
			relation.matching-rule.user-friendly-name=Vergleichs-Regel (Matching Rule)
			relation.matching-rule.user-friendly-plural-name=Vergleichs-Regeln (Matchjing Rules)
			relation.matching-rule.synopsis=Vergleichs-Regeln definieren eine Sammlung von Regeln um Matchin-Operationen gegen Assertion-Werte durchzuf\u00fchren.
			relation.matching-rule.description=Vergleichs-Regeln sind oft mit Attribut-Syntaxen assoziiert und werden dazu benutzt um Werte in bezug auf deren Syntax zu vergleichen. Zum Beispiel, die distinguishedNameEqualityMatch Vergleichs-Regel kann verwendet werden um festzustellen ob zwei DNs gleich sind. Die distinguishedNameEqualityMatch Vergleichs-Regel kann Zeichen wie Leerzeichen die um Kommas oder Gleichheitszeichen sind, unterschiedliche Gross und Kleinschreibung von Attributnamen, usw. ignorieren.
			relation.monitor-provider.user-friendly-name=Monitor Provider
			relation.monitor-provider.user-friendly-plural-name=Monitor Providers
			relation.monitor-provider.synopsis=Monitor Providers can be used to provide information about the state of the server or one of its components.
			@@ -93,13 +93,13 @@
			relation.password-validator.synopsis=Password Validators are responsible for determining whether a proposed password is acceptable for use and could include checks like ensuring it meets minimum length requirements, that it has an appropriate range of characters, or that it is not in the history.
			relation.password-validator.description=The password policy for a user specifies the set of password validators that should be used whenever that user provides a new password. In order to activate a password validator, the corresponding configuration entry must be enabled, and the DN of that entry should be included in the password-validator attribute of the password policy in which you want that validator active. All password validator configuration entries must contain the password-validator structural objectclass.
			relation.plugin-root.user-friendly-name=Plugin Root
			relation.plugin-root.synopsis=The Plugin Root defines the parent entry for all plug-ins defined in the server.
			relation.plugin-root.description=It can also include configuration attributes that define the order in which those plug-ins are to be loaded and invoked.
			relation.plugin-root.synopsis=Der Plugin Root ist der \u00fcbergeordnete Eintrag f\u00fcr alle um Server befindlichen Plugins.
			relation.plugin-root.description=Er kann auch Konfigurationsatribute beinhalten welche die Reihenfolge in welcher Plugens geladen und Aufgerufen werden festlegen.
			relation.root-dn.user-friendly-name=Root DN
			relation.root-dn.synopsis=The Root DN configuration contains all the Root DN Users defined in the Directory Server. In addition, it also defines the default set of privileges that Root DN Users automatically inherit.
			relation.root-dse-backend.user-friendly-name=Root DSE Backend
			relation.root-dse-backend.synopsis=The Root DSE Backend contains the Directory Server root DSE.
			relation.root-dse-backend.description=This is a special meta-backend that dynamically generates the root DSE entry for base-level searches and simply redirects to other backends for operations in other scopes.
			relation.root-dse-backend.user-friendly-name=Wurzel DSE Backend (Root DSE Backend)
			relation.root-dse-backend.synopsis=Der Wurzel DSE Backend enth\u00e4lt den Directory Server Wurzel DSE.
			relation.root-dse-backend.description=Das ist ein spezielles Meta-Backend welches dynamisch den Wurzel DSE Eintrag f\u00fcr Basis-Level Suchen und einfache Weiterleitungen zu anderen Backends (f\u00fcr Operationen in anderen Bereichen).
			relation.sasl-mechanism-handler.user-friendly-name=SASL Mechanism Handler
			relation.sasl-mechanism-handler.user-friendly-plural-name=SASL Mechanism Handlers
			relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDS Directory Server.
			@@ -108,20 +108,20 @@
			relation.synchronization-provider.user-friendly-plural-name=Synchronization Providers
			relation.synchronization-provider.synopsis=Synchronization Providers are responsible for handling synchronization of the Directory Server data with other OpenDS instances or other data repositories.
			relation.synchronization-provider.description=The OpenDS Directory Server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDS, one or more replication servers are created in the environment. The replication servers typically do not store user data but keep a log of all changes made within the topology. Each Directory Server instance in the topology is pointed at the replication servers. This plan simplifies the deployment and management of the environment. Although you can run the replication server on the same system (or even in the same instance) as the Directory Server, the two servers can be separated onto different systems. This approach can provide better performance or functionality in large environments.
			relation.trust-manager-provider.user-friendly-name=Trust Manager Provider
			relation.trust-manager-provider.user-friendly-plural-name=Trust Manager Providers
			relation.trust-manager-provider.synopsis=Trust Manager Providers determine whether to trust presented certificates.
			relation.trust-manager-provider.user-friendly-name=Trust-Manager-Provider
			relation.trust-manager-provider.user-friendly-plural-name=Trust-Manager-Provider
			relation.trust-manager-provider.synopsis=Trust-Manager-Provider entschiden ob angegebenen Zertifikaten Vertraut werden soll.
			relation.virtual-attribute.user-friendly-name=Virtual Attribute
			relation.virtual-attribute.user-friendly-plural-name=Virtual Attributes
			relation.virtual-attribute.synopsis=Virtual Attributes are responsible for dynamically generating attribute values that appear in entries but are not persistently stored in the backend.
			relation.virtual-attribute.description=Virtual attributes are associated with a virtual attribute provider, which contains the logic for generating the value.
			relation.workflow.user-friendly-name=Workflow
			relation.workflow.user-friendly-plural-name=Workflows
			relation.workflow.synopsis=The Workflow is a list of processing steps (Work Flow Elements) that are applied to data as it is retrieved from the Directory Server.
			relation.workflow-element.user-friendly-name=Workflow Element
			relation.workflow-element.user-friendly-plural-name=Workflow Elements
			relation.workflow-element.synopsis=Workflow Elements implement a single processing step in a Work Flow.
			relation.workflow-element.description=A Workflow Element can perform a task such as mapping DNs, renaming attributes, filtering attributes, joining data sources, proxying, or load-balancing. The simplest Workflow Element is the Local Backend Work Flow Element, which routes data to a Backend.
			relation.work-queue.user-friendly-name=Work Queue
			relation.work-queue.synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
			relation.work-queue.description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
			relation.workflow.synopsis=Ein Workflow ist eine Liste von einzelnen Arbeitsschritten (Work Flow Elements) die auf Daten angewandt werden die aus einem Directory Server bezogen werden.
			relation.workflow-element.user-friendly-name=Workflow-Element
			relation.workflow-element.user-friendly-plural-name=Workflow-Elemente
			relation.workflow-element.synopsis=Workflow-Elemente implementieren einen einzelnen Verarbeitungsschritt in einem Workflow.
			relation.workflow-element.description=Ein Workflow Element kann z.b. einen Arbeitsschritt wie mappen von DNs, Umbenennen von Attributen, Filtern von Attributen, Datenquellen verbinden, Proxying oder Loadbalancing ausf\u00fchren. Das einfachste Workflow-Element ist das Local Backend Workflow-Element, welches Daten zum Backend routet.
			relation.work-queue.user-friendly-name=Arbeitsvorrat (Work Queue)
			relation.work-queue.synopsis=Der Arbeitsvorrat (Work Queue) bietet die Konfiguration des Server Arbeitsvorrates (Server Work Queue) an. Die Server Work Queue is verantworlich daf\u00fcr, dass Requests die von Clients empfangen werden, in einer bestimmten Zeit verarbeitet werden.
			relation.work-queue.description=Es kann nur eine Work Queue in einem Server definiert werden. Wenn ein Connection-Handler einen Client Request empf\u00e4ngt, Stellt der Connection-Handler diesen Request in die Work Queue, damit der Request richtig verarbeitet werden kann.