external-software/github_OpenIdentityPlatform_OpenDJ.git

			@@ -1,6 +1,6 @@
			user-friendly-name=Root
			user-friendly-plural-name=Roots
			synopsis=The root configuration provides an entry point to the rest of the OpenDS Directory Server configuration.
			synopsis=The root configuration provides an entry point to the rest of the OpenDJ configuration.
			tag.core-server.synopsis=Core server
			tag.database.synopsis=Caching and back-ends
			tag.logging.synopsis=Logging
			@@ -45,7 +45,7 @@
			relation.extension.synopsis=The Extension allows to extend the configuration with new type of objects.
			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.global-configuration.synopsis=The Global contains properties that affect the overall operation of the OpenDJ .
			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.
			@@ -102,12 +102,12 @@
			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.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.
			relation.sasl-mechanism-handler.synopsis=The SASL mechanism handler configuration entry is the parent for all SASL mechanism handlers defined in the OpenDJ .
			relation.sasl-mechanism-handler.description=SASL mechanism handlers are responsible for authenticating users during the course of processing a SASL (Simple Authentication and Security Layer, as defined in RFC 4422) bind.
			relation.synchronization-provider.user-friendly-name=Synchronization Provider
			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.synchronization-provider.description=The OpenDJ 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.