mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git
opends/src/admin/messages/RootCfgDefn.properties
@@ -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 @@ -8,8 +8,8 @@ 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.synopsis=Access Control Handlers manage the application-wide access control. The OpenDJ 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 OpenDJ 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.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. @@ -18,7 +18,7 @@ relation.administration-connector.description=It is a dedicated entry point for administration. relation.alert-handler.user-friendly-name=Alert Handler relation.alert-handler.user-friendly-plural-name=Alert Handlers relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the Directory Server. relation.alert-handler.synopsis=Alert Handlers are used to notify administrators of significant problems or notable events that occur in the OpenDJ directory server. relation.attribute-syntax.user-friendly-name=Attribute Syntax relation.attribute-syntax.user-friendly-plural-name=Attribute Syntaxes relation.attribute-syntax.synopsis=Attribute Syntaxes define the type of data that may be stored in an attribute with that syntax. A syntax is generally associated with a set of matching rules that indicate how to perform matching operations against values of that syntax. @@ -36,7 +36,7 @@ relation.crypto-manager.synopsis=The Crypto Manager provides a common interface for performing compression, decompression, hashing, encryption and other kinds of cryptographic operations. 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. relation.entry-cache.synopsis=Entry Caches are responsible for caching entries which are likely to be accessed by client applications in order to improve OpenDJ directory server performance. relation.extended-operation-handler.user-friendly-name=Extended Operation Handler relation.extended-operation-handler.user-friendly-plural-name=Extended Operation Handlers relation.extended-operation-handler.synopsis=Extended Operation Handlers processes the different types of extended operations in the server. @@ -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. @@ -96,18 +96,18 @@ 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.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-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.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.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 directory server. 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.synopsis=Synchronization Providers are responsible for handling synchronization of the directory server data with other OpenDJ instances or other data repositories. relation.synchronization-provider.description=The OpenDJ directory server takes a centralized approach to replication, rather than the point-to-point approach taken by Sun Java System Directory Server. In OpenDJ, 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. @@ -117,7 +117,7 @@ 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.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.
