Deprecated
The functionality listed here is deprecated, and likely to be removed in a future release.
Since DS 8.0
-
The HTTP OAuth2 OpenAM authorization scheme is deprecated.
-
The
ds-rlim-lookthrough-limitsetting is no longer deprecated. -
The following table lists deprecated metrics and their replacements:
Deprecated metric Use this instead ds-mon-backend-degraded-indexds-mon-backend-untrusted-indexds-mon-backend-degraded-index-countds-mon-backend-untrusted-index-countds_backend_degraded_index_countds_backend_untrusted_index_count
Since DS 7.5.1
-
The
setup-profile --instancePathis deprecated.Run the
setup-profilecommand located with the server instance.
Since DS 7.5
-
The Prometheus endpoint configuration property
legacy-formatis deprecated.Update your applications to work with the Prometheus text format.
-
To prepare for compliance with the OpenMetrics standard, all Prometheus counter metrics end in
_totalgoing forward.The following table lists deprecated metrics with their replacements:
Deprecated counter Use this instead ds_connection_handlers_ldap_abandoned_requestsds_connection_handlers_ldap_abandoned_requests_totalds_replication_replica_replayed_internal_updatesds_replication_replica_replayed_internal_updates_totalds_replication_replica_replayed_updates_conflicts_resolvedds_replication_replica_replayed_updates_conflicts_resolved_totalds_replication_replica_replayed_updates_conflicts_unresolvedds_replication_replica_replayed_updates_conflicts_unresolved_totalds_replication_replica_sent_updatesds_replication_replica_sent_updates_totalds_replication_replica_updates_already_in_progressds_replication_replica_updates_already_in_progress_total
Since DS 7.4.2
-
The
dsrepl start-disaster-recoveryanddsrepl end-disaster-recoverycommands are deprecated.For instructions on what to use, refer to the disaster recovery documentation instead.
Since DS 7.4
-
Support for REST to LDAP is deprecated in favor of HDAP for future applications.
REST to LDAP remains supported as documented for DS 7.3.
For details about HDAP, refer to Use HDAP.
-
Support for
/admin/configis deprecated.Use the
dsconfigcommand to change the DS server configuration. -
Support for
/metrics/apiis deprecated.Use Prometheus for HTTP monitoring instead. For details, refer to HTTP-based monitoring.
-
Support for the backwards-compatible file-based access log publisher is deprecated.
Use the JSON format log publishers, which new DS servers use by default since the 5.0 release.
-
Support for the JMX connection handler is deprecated.
JMX MBeans remain supported.
Since DS 7.3.5
-
The
dsrepl start-disaster-recoveryanddsrepl end-disaster-recoverycommands are deprecated.For instructions on what to use, refer to the disaster recovery documentation instead.
Since DS 7.2.5
-
The
dsrepl start-disaster-recoveryanddsrepl end-disaster-recoverycommands are deprecated.For instructions on what to use, refer to the disaster recovery documentation instead.
Since DS 7.2
-
The
ds-pwp-last-login-timeattribute, which has directory string syntax, is deprecated.Use the new
ds-last-login-timeattribute instead. For an example, refer to Active accounts. -
Support for CSV, Elasticsearch, JDBC, JMS, Splunk, and Syslog access logs is deprecated.
-
The DSML gateway is deprecated.
For deployments that require HTTP access to directory data, consider HDAP as an alternative.
Since DS 7.1.8
-
The
dsrepl start-disaster-recoveryanddsrepl end-disaster-recoverycommands are deprecated.For instructions on what to use, refer to the disaster recovery documentation instead.
Since DS 7.1.3
-
The following Prometheus counter metrics are deprecated:
-
ds_connection_handlers_ldap_abandoned_requests{ldap_handler} -
ds_replication_replica_replayed_internal_updates{domain_name,server_id} -
ds_replication_replica_replayed_updates_conflicts_resolved -
ds_replication_replica_replayed_updates_conflicts_unresolved -
ds_replication_replica_sent_updates -
ds_replication_replica_updates_already_in_progress{domain_name,server_id}
They are expected to be replaced with metrics whose names end in
_totalin a future release. -
Since DS 7.1
-
The previous format for password file options is deprecated. The options remain supported until removal, but are now hidden in online help. This affects the following options:
Deprecated form Use this form --bindPasswordFile--bindPassword:file--deploymentKeyPasswordFile--deploymentIdPassword:file--keyStorePasswordFile--keyStorePassword:file--keyStorePasswordFilePath(1)--monitorUserPasswordFile--monitorUserPassword:file--rootUserPasswordFile--rootUserPassword:file--trustStorePasswordFile--trustStorePassword:file--trustStorePasswordFilePath(1)(1) The
--keyStorePasswordFilePathand--trustStorePasswordFilePathoptions apply only to thesetup. They retain the path to the file in the configuration. The other options copy the cleartext password at setup time. -
The
dsrepl add-local-server-to-pre-7-0-topologycommand--masterKeyPairCertAliasand--rootCaCertAliasoptions are deprecated. The command now finds the certificates by introspecting the configuration.The options are now hidden in online help.
Since DS 7.0
-
Support for SNMP.
DS software provides better options for monitoring servers, including support for Prometheus, Graphite, and LDAP. For details, refer to Monitoring.
DS server software also includes a sample monitoring dashboard for Prometheus and Grafana, which is described in
opendj/samples/grafana/README.md. -
The
pwdValidatorPolicyobject class.For subentry password policies, use the object classes derived from
ds-pwp-validatorinstead. -
Reversible password storage schemes, and the
cn=admin database DN andadminDatabackend used to support them. This includes the following password storage schemes:-
3DES -
AES -
Blowfish -
RC4
The
3DES,Blowfish, andRC4are supported for compatibility purposes only. If you must use reversible encryption, use theAESscheme. -
-
The
ds-rlim-lookthrough-limitsetting is deprecated.
Since DS 6.5
-
Regarding replication monitoring metrics, including those deprecated since 6.0:
In mixed topologies, a directory server version 6 or earlier connected to a replication server version 6.5 or later cannot consume messages about other servers going offline. The monitoring framework reflects this as a delay on the directory server that could not consume the message.
The delay is calculated correctly again once all servers in the topology are upgraded to at least version 6.5, or when the offline server comes back online and has seen a change to directory data.
Monitor replication delay instead of using the deprecated metrics. For details, refer to Replication delay (LDAP) or Replication delay (Prometheus).