Configuration Changes Requiring Administrative Action

This page lists the set of configuration properties that require some form of administrative action for changes to take full effect.

Note that any changes to the java.properties file (which is used to specify the Java runtime and JVM options that should be used when running the Data Governance Server and associated tools) require that the dsjavaproperties tool be run to apply those changes. If the changes impact the Java runtime or JVM arguments used to run the Data Governance Server itself, then the server must be restarted.

Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Alarm Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Alert Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Backup Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Changelog Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration
• db-directory - The Data Governance Server must be restarted for changes to this configuration property to take full effect. Modification requires that the Data Governance Server be stopped, the database directory manually relocated, and then the Data Governance Server restarted. While the Data Governance Server is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• db-cache-percent - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• je-property - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• changelog-write-queue-capacity - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

Config File Handler Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Encryption Settings Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

JE Backend

• is-private-backend - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-directory - The Data Governance Server must be restarted for changes to this configuration property to take full effect. Modification requires that the Data Governance Server be stopped, the database directory manually relocated, and then the Data Governance Server restarted. While the Data Governance Server is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• db-num-cleaner-threads - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-cleaner-min-utilization - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-evictor-critical-percentage - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-log-file-max - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-logging-level - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• je-property - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-cache-percent - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• default-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2entry-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• dn2id-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2children-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2subtree-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• dn2uri-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• index-entry-limit - If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit.
• composite-index-entry-limit - If any composite index keys have already reached this limit, those composite indexes must be rebuilt before they will be allowed to use the new limit.
• id2children-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2children keys that had already hit the previous limit.
• id2subtree-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2subtree keys that had already hit the previous limit.
• db-txn-write-no-sync - The JE Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-recent-changes - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

Large Attribute Backend

• enabled - DEPRECATION NOTE: The large attribute backend has been deprecated. It will continue to be supported for existing deployments already using the large attribute feature, but new deployments wishing for similar behavior should configure uncached attributes rather than large attributes.
• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration
• is-private-backend - The Large Attribute Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-cache-percent - The Large Attribute Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• default-cache-mode - The Large Attribute Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Local DB Backend

• uncached-id2entry-cache-mode - The Local DB Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDIF Backend

• is-private-backend - The LDIF Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ldif-file - The LDIF Backend must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Monitor Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Schema Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Task Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

Trust Store Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact Ping Identity support to discuss this configuration

HTTP Connection Handler

• listen-address - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-ssl - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-cert-nickname - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• http-servlet-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• web-application-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-protocol - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-cipher-suite - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• key-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• trust-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-request-handlers - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• enable-multipart-mime-parameters - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-forwarded-headers - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• http-request-header-size - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• response-header - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-client-auth-policy - The HTTP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

JMX Connection Handler

• listen-port - The JMX Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-ssl - The JMX Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-cert-nickname - The JMX Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDAP Connection Handler

• listen-address - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.
• use-ssl - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• allow-start-tls - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.
• ssl-cert-nickname - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• max-cancel-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-accept-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-request-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-client-auth-policy - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• accept-backlog - The LDAP Connection Handler must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Crypto Manager

• ssl-cert-nickname - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

HTTP External Server

• hostname-verification-method - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• key-manager-provider - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• trust-manager-provider - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Global Configuration

• location - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted. This modification must also be made to the Server Instance representing this server in the topology registry. This will ensure that topology-related operations involving communication with other servers prefer servers in the same location as this server. For example, when replication data is initialized on this server using a topology file, then another server in the same location as this server will be used, if available.
• force-as-master-for-mirrored-data - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.
• encryption-settings-cipher-stream-provider - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.
• allow-insecure-local-jmx-connections - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• maximum-shutdown-time - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.
• jmx-use-legacy-mbean-names - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

HTTP Servlet Extension

• response-header - HTTP Connection Handlers hosting this HTTP Servlet Extension must be disabled and then re-enabled, or the server restarted, in order for this change to take effect.

Availability State HTTP Servlet Extension

• base-context-path - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Config HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Consent HTTP Servlet Extension

• bearer-token-auth-enabled - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• basic-auth-enabled - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• identity-mapper - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• access-token-validator - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Delegated Admin HTTP Servlet Extension

• basic-auth-enabled - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• access-token-validator - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Directory REST API HTTP Servlet Extension

• basic-auth-enabled - The Data Governance Server must be restarted for changes to this configuration property to take full effect. For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• access-token-validator - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

File Server HTTP Servlet Extension

• base-context-path - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Gateway HTTP Servlet Extension

• request-limit - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• response-limit - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SCIM HTTP Servlet Extension

• base-context-path - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• debug-enabled - The Data Governance Server debug logger must be enabled and correctly configured for the debug messages to be forwarded.

LDAP Mapped SCIM HTTP Servlet Extension

• oauth-token-handler - The Data Governance Server must be restarted for changes to this configuration property to take full effect. The OAuth Token Handler changes will not take effect until the associated HTTP Connection Handler is disabled and re-enabled, or until the server is restarted.
• basic-auth-enabled - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• include-ldap-objectclass - If you have specified a large number of object classes or used the '*' value you should ensure that the Data Governance Server has been allocated a sufficient amount of memory (typically at least 512MB) to host the HTTP endpoints.

Metrics HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Open Banking HTTP Servlet Extension

• path-prefix - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• consent-definition-id - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SCIM2 HTTP Servlet Extension

• base-context-path - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• debug-enabled - The Data Governance Server debug logger must be enabled and correctly configured for the debug messages to be forwarded.

Sideband API HTTP Servlet Extension

• request-limit - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDAP SDK Debug Logger

• queue-size - The LDAP SDK Debug Logger must be restarted if this property is changed and the asynchronous property is set to true.
• sign-log - The LDAP SDK Debug Logger must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The LDAP SDK Debug Logger must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Writer Based Access Log Publisher

• queue-size - The Writer Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Admin Alert Access Log Publisher

• queue-size - The Admin Alert Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Access Log Publisher

• log-file - The File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Debug Access Log Publisher

• log-file - The Debug Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Debug Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Debug Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Debug Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Audit Log Publisher

• log-file - The File Based Audit Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Audit Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Audit Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The File Based Audit Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Access Log Publisher

• log-file - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Scripted File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JDBC Based Access Log Publisher

• queue-size - The JDBC Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JSON Access Log Publisher

• log-file - The JSON Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The JSON Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The JSON Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The JSON Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Operation Timing Access Log Publisher

• log-file - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Operation Timing Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Third Party File Based Access Log Publisher

• log-file - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Third Party File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Common Log File HTTP Operation Log Publisher

• log-file - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Common Log File HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Detailed HTTP Operation Log Publisher

• log-file - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Detailed HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Debug Log Publisher

• log-file - The File Based Debug Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Debug Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Debug Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The File Based Debug Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Error Log Publisher

• log-file - The File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Error Log Publisher

• log-file - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Scripted File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JDBC Based Error Log Publisher

• queue-size - The JDBC Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JSON Error Log Publisher

• log-file - The JSON Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The JSON Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The JSON Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The JSON Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Syslog Based Error Log Publisher

• queue-size - The Syslog Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Third Party File Based Error Log Publisher

• log-file - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Third Party File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Policy Decision Log Publisher

• queue-size - The File Based Policy Decision Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Policy Decision Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Policy Decision Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Policy Decision Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

File Based Sync Log Publisher

• log-file - The File Based Sync Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Sync Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Sync Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The File Based Sync Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Sync Failed Ops Log Publisher

• log-file - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Sync Failed Ops Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Writer Based Trace Log Publisher

• queue-size - The Writer Based Trace Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Trace Log Publisher

• log-file - The File Based Trace Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Trace Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• encrypt-log - The File Based Trace Log Publisher must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Host System Monitor Provider

• enabled - Enabling host system cpu, memory, disk and network interface I/O monitoring requires running an external collector helper process except on Linux systems. Notes: - Enabling the host system monitor does not require restarting the server on Linux systems. - Enabling the host system monitor provider on UNIX (non-Linux) requires restarting the server. Changes to disk-devices and network-devices cannot be validated until the server is restarted. - Host system monitoring is not available on Windows systems.

Password Policy

• enable-debug - When enable-debug is set to true, additional configuration changes are required. 1. Create a Debug Target targeting the password policy class: dsconfig create-debug-target --publisher-name "File-Based Debug Logger" --target-name com.unboundid.directory.server.core.PasswordPolicyState --set debug-level:verbose 2. Enable the debug logger: dsconfig set-log-publisher-prop --publisher-name "File-Based Debug Logger" --set enabled:true With the default configuration settings, debugging information will be written to the logs/debug file.
• idle-lockout-interval - Last login time tracking is required for idle account lockout to work properly. If you are enabling idle account lockout, then you should ensure that the last-login-time-attribute and last-login-time-format properties are also defined and that last login time tracking has been enabled long enough so that user accounts have had time to be marked with last login times. Ideally, last login time tracking should be enabled for at least as long as the idle lockout interval to ensure that users are not incorrectly locked out merely because their accounts do not have last login time information.

Argon2 Password Storage Scheme

• enabled - This password storage scheme implementation requires the Bouncy Castle JCE provider, which is not included with the Data Governance Server, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.65 of the library, which can be obtained from the Bouncy Castle website using the link https://www.bouncycastle.org/download/bcprov-jdk15on-165.jar. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

Base64 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Bcrypt Password Storage Scheme

• enabled - This password storage scheme implementation requires the Bouncy Castle JCE provider, which is not included with the Data Governance Server, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.65 of the library, available in file https://www.bouncycastle.org/download/bcprov-jdk15on-165.jar. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

Clear Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

MD5 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

PBKDF2 Password Storage Scheme

• digest-algorithm - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

RC4 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

SHA1 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Salted MD5 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Salted SHA1 Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Scrypt Password Storage Scheme

• enabled - This password storage scheme implementation requires the Bouncy Castle JCE provider, which is not included with the Data Governance Server, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.65 of the library, which can be obtained from the Bouncy Castle website using the link https://www.bouncycastle.org/download/bcprov-jdk15on-165.jar. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

Triple DES Password Storage Scheme

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Plugin

• plugin-type - The Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Attribute Mapper Plugin

• plugin-type - The Attribute Mapper Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Change Subscription Notification Plugin

• plugin-type - The Change Subscription Notification Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Changelog Password Encryption Plugin

• plugin-type - The Changelog Password Encryption Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Composed Attribute Plugin

• plugin-type - The Composed Attribute Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

DN Mapper Plugin

• plugin-type - The DN Mapper Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Delay Plugin

• plugin-type - The Delay Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Encrypt Attribute Values Plugin

• plugin-type - The Encrypt Attribute Values Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Entry UUID Plugin

• plugin-type - The Entry UUID Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Internal Search Rate Plugin

• plugin-type - The Internal Search Rate Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDAP Result Code Tracker Plugin

• plugin-type - The LDAP Result Code Tracker Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Last Mod Plugin

• plugin-type - The Last Mod Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Monitor History Plugin

• log-file - The Monitor History Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Pass Through Authentication Plugin

• plugin-type - The Pass Through Authentication Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Periodic GC Plugin

• plugin-type - The Periodic GC Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Periodic Stats Logger Plugin

• log-file - The Periodic Stats Logger Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Pre Update Config Plugin

• plugin-type - The Pre Update Config Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Processing Time Histogram Plugin

• plugin-type - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• histogram-category-boundary - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. The Data Metrics Server can only aggregate response-time data when the boundary values are the same across both time and monitored servers. If you change the boundary values on one monitored server, you should change them on all monitored servers.
• separate-monitor-entry-per-tracked-application - When setting this option to true, you must also set the per-application-ldap-stats property in the Stats Collector Plugin to per-application-only.

Referential Integrity Plugin

• plugin-type - The Referential Integrity Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Referral On Update Plugin

• plugin-type - The Referral On Update Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SNMP Master Agent Plugin

• listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• notification-target-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• notification-target-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-snmp-version - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• community-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-security-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-security-level - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-worker-threads - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SNMP Subagent Plugin

• context-name - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-address - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-port - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-worker-threads - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Seven Bit Clean Plugin

• plugin-type - The Seven Bit Clean Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Sub Operation Timing Plugin

• plugin-type - The Sub Operation Timing Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Unique Attribute Plugin

• plugin-type - The Unique Attribute Plugin must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

UnboundID Ms Chap V2 SASL Mechanism Handler

• enabled - This SASL mechanism handler implementation requires the Bouncy Castle JCE provider, which is not included with the Data Governance Server, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.64 of the library, available in file https://www.bouncycastle.org/download/bcprov-jdk15on-165.jar. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

UnboundID TOTP SASL Mechanism Handler

• prevent-totp-reuse - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact Ping Identity for more information.

Directory Server Instance

• replication-set-name - The Data Governance Server must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

LDAP Store Adapter

• load-balancing-algorithm - The LDAP Store Adapter must be disabled and re-enabled (or the Data Governance Server restarted) for changes to this configuration property to take full effect. Changes to this property will not take effect until the LDAP Store Adapter is restarted.
• auxiliary-ldap-objectclass - The Data Governance Server must be restarted for changes to this configuration property to take full effect. Changes to this property will not take effect until the server is restarted.

Third Party Store Adapter

• extension-argument - The Data Governance Server must be restarted for changes to this configuration property to take full effect. Changes to this property will not take effect until the server is restarted.

Web Application Extension

• base-context-path - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• war-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• document-root-directory - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• deployment-descriptor-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• temporary-directory - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• init-parameter - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Console Web Application Extension

• ldap-server - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• trust-store-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• trust-store-type - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• log-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• complexity - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.