Notes covering ForgeRock® Directory Services features, fixes, and known issues.

• DS 6.5.6 Maintenance Release

  DS 6.5.6 is the latest release targeted for DS 6.5.x deployments, and can be downloaded from the ForgeRock Backstage website. To view the list of fixes in this release, see DS 6.5.6.

  The release can be deployed as an initial deployment or updated from an existing DS 6.5.x deployment.

• The supportextract command now collects environment variables used in configuration expressions.

• DS servers now more effectively calculate reservable memory when using G1 garbage collection, and reduce the risk of long fsync pauses.

  This change introduces a ds-mon-db-cache-size-total metric to track the maximum size of the database cache. It also changes the ds-mon-db-log-size-active metric to reflect only live data.

• The supportextract command now uses the jcmd command, if available, for heap dumps. Otherwise, it uses the jmap command.

• There are no new features introduced in DS 6.5.4, only bug fixes.

This release of Directory Services software includes the following new feature:

• ADS-Certificate Key Pair and Peer DS Servers' Trusted Public Keys Support in PKCS#11 Modules

  DS servers now support storing the ads-certificate key pair and peer DS servers' trusted public keys in a PKCS#11 module, such as a hardware security module (HSM). This means you can store the keys used to secure replication traffic and to protect symmetric keys in an HSM. Previously, DS servers supported use of a PKCS#11 module only to store the keys used to secure other communications.

  Note

  DS servers support PKCS#11 modules through the JVM. How to configure the JVM to allow DS servers to use your module, how to generate keys in the module, and how to export and import public key certificates all depend on your specific HSM/PKCS#11 module.

  For details on how to perform such actions, see your PKCS#11 module's documentation.

  Before trying this feature, perform these tests:

  • Test that the PKCS#11 module supports multiple aliases for the same certificate.

  • Test that the PKCS#11 module supports generating a key pair with an RSA self-signed certificate and a key size of 2048 bits.

  • Test the replication topology using the default JKS ads-truststore implementation.

    Verify that replication functions properly before using the PKCS#11 module.

  After validating the results of the tests, use the new feature by performing these steps for each server:

  1. Configure JVM security to enable use of the PKCS#11 module for the server.

  2. Generate a key pair using an RSA self-signed certificate and a key size of 2048 bits with the alias ads-certificate on the PKCS#11 module.

  3. After generating the key pair:

     1. Export the ads-certificate certificate, and reimport it on the PKCS#11 module using the MD5 fingerprint as the certificate alias.

        For example, if the ads-certificate certificate MD5 fingerprint is 07:35:80:D8:F3:CE:E1:39:9C:D0:73:DB:6C:FA:CC:1C, reimport the certificate with the alias 073580D8F3CEE1399CD073DB6CFACC1C.

     2. Prepare LDIF to update cn=admin data for the new certificate.

        The LDIF adds the new certificate as an instance key, and sets the key ID for the current server to use the key. In the following example LDIF, the certificate alias is 073580D8F3CEE1399CD073DB6CFACC1C, and the server hostname:admin-port combination is opendj.example.com:4444:

        dn: ds-cfg-key-id=073580D8F3CEE1399CD073DB6CFACC1C,cn=instance keys, cn=admin data
        changetype: add
        ds-cfg-key-id: 073580D8F3CEE1399CD073DB6CFACC1C
        ds-cfg-public-key-certificate;binary:: MIIB6zCCAVSgAwIBAgIEDKSUFjANBgkqhkiG9w0BA
        QUFADA6MRswGQYDVQQKExJPcGVuREogQ2VydGlmaWNhdGUxGzAZBgNVBAMTEm9wZW5hbS5leGFtcGxl
        LmNvbTAeFw0xMzAyMDcxMDMwMzNaFw0zMzAyMDIxMDMwMzNaMDoxGzAZBgNVBAoTEk9wZW5ESiBDZXJ
        0aWZpY2F0ZTEbMBkGA1UEAxMSb3BlbmFtLmV4YW1wbGUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNAD
        CBiQKBgQCfGLAiUOz4sC8CM9T5DPTk9V9ErNC8N59XwBt1aN7UjhQl4/JZZsetubtUrZBLS9cRrnYdZ
        cpFgLQNEmXifS+PdZ0DJkaLNFmd8ZX0spX8++fb4SkkggkmNRmi1fccDQ/DHMlwl7kk884lXummrzcD
        GbZ7p4vnY7y7GmD1vZSP+wIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAJciUzUP8T8A9VV6dQB0SYCNG1o
        7IvpE7jGVZh6KvM0m5sBNX3wPbTVJQNij3TDm8nx6yhi6DUkpiAZfz/OBL5k+WSw80TjpIZ2+klhP1s
        srsST4Um4fHzDZXOXHR6NM83XxZBsR6MazYecL8CiGwnYW2AeBapzbAnGn1J831q1q
        objectClass: top
        objectClass: ds-cfg-instance-key
        
        dn: cn=opendj.example.com:4444,cn=Servers,cn=admin data
        changetype: modify
        replace: ds-cfg-key-id
        ds-cfg-key-id: 073580D8F3CEE1399CD073DB6CFACC1C

        Do not yet update cn=admin data. You must not change the server key ID until the server is ready to use the PKCS#11 module.

  4. Edit the ads-truststore trust manager provider configuration to access the PKCS#11 module with the following properties:

     trust-store-file

     Leave this unchanged.

     trust-store-pin

     Set this to the PIN for the PKCS#11 module.

     You can avoid exposing secrets in the configuration by using expressions. For details, see "Using Configuration Property Value Substitution" in the Administration Guide.

     trust-store-type

     Set this to PKCS11.

  5. Stop the DS server.

  6. Using the ldifmodify command while the server is stopped, update cn=admin data for the server with the LDIF you prepared.

     This step changes the key ID for the server, letting it use its keys held in the PKCS#11 module.

  7. On another, running server replica, use the ldapmodify command to update cn=admin data for the server with the LDIF you prepared.

     Replication propagates the change to the other running server replicas.

     This step changes the key ID for the server, letting other servers trust its new certificate once it restarts.

  8. Restart the DS server.

• There are no new features introduced in DS 6.5.2, only bug fixes.

• There are no new features introduced in DS 6.5.1, only bug fixes.

This release of Directory Services software includes the following new features:

• Connection Limiting

  DS servers now allow you to limit the number of concurrent connections per client.

  For details, see "Limiting and Restricting Client Connections" in the Administration Guide.

• Data Distribution

  DS proxy servers now support simple, non-elastic data distribution.

  You can configure a proxy server to equitably distribute LDAP write requests across multiple replication partitions to scale the directory service horizontally. As the present implementation does not permit elastic scaling or data redistribution, make sure that you understand the documented constraints of the present implementation before deploying it in production.

  For an example, see "Scaling Out Using Data Distribution" in the Deployment Guide.

  The mechanism is described in "Routing Requests to Remote Directory Servers" in the Administration Guide.

• Database Caching

  A new DS directory server uses shared cache by default for all JE database backends. As a result, you are no longer required to set the database cache size using the db-cache-percent or db-cache-size setting for each backend.

  It remains possible to use these settings if necessary by configuring them appropriately. For details, see "Database Cache Settings" in the Administration Guide.

• Logging

  • DS servers now support sending access log messages to standard output.

    For details, see "Sending JSON Access Logs to Standard Output" in the Administration Guide.

    When the new handler is used, standard output from the server includes a mix of JSON for access messages and non-JSON DS-format server event messages.

  • Common Audit logging now supports blacklisting log message fields to prevent them from showing up in log messages.

    For an example, see "Blacklisting Log Message Fields" in the Administration Guide.

  • Common Audit logging now supports writing multiple file-based logs to the same directory by setting a different log-file-name-prefix for each file-based log.

• Monitoring

  DS servers now provide health status checks for anonymous requests over HTTP and LDAP. This allows a remote application to check that a server is "alive" and "healthy".

  Anonymous HTTP requests can retrieve "alive" and "healthy" status codes. Anonymous LDAP requests can retrieve "alive" and "healthy" boolean values.

  The "alive" and "healthy" status indicates that the server has passed its own internal tests. It is not, however, a guarantee that the server is free from other errors. If a server is not "alive," it requires administrative intervention. If a server is not "healthy," temporarily route requests to another server.

  When a server is not "alive" or "healthy," a user with privileges to read monitoring information receives health status error messages in the body of the HTTP response, and can obtain health status error messages over LDAP as described below. No error messages are returned in response to anonymous requests.

  For examples demonstrating how to use this feature, see the following documentation:

  • "Monitoring Liveness over HTTP" in the Administration Guide

  • "Monitoring Ability to Handle Requests Over HTTP" in the Administration Guide

  • "Monitoring Health Status With Prometheus" in the Administration Guide

  • "Monitoring Health Status Anonymously Over LDAP" in the Administration Guide

  • "Monitoring Health Status Details Over LDAP" in the Administration Guide

  When you upgrade DS servers to this release, the anonymously accessible HTTP endpoints are not configured. To add the endpoints on an upgraded server that lacks them, use the dsconfig command:

      $ dsconfig \
      create-http-endpoint \
      --endpoint-name /alive \
      --type alive-endpoint \
      --set enabled:true \
      --set authorization-mechanism:HTTP Anonymous \
      --set authorization-mechanism:HTTP Basic \
      --hostname opendj.example.com \
      --port 4444 \
      --bindDN "cn=Directory Manager" \
      --bindPassword password \
      --trustAll \
      --no-prompt
      $ dsconfig \
      create-http-endpoint \
      --endpoint-name /healthy \
      --type healthy-endpoint \
      --set enabled:true \
      --set authorization-mechanism:HTTP Anonymous \
      --set authorization-mechanism:HTTP Basic \
      --hostname opendj.example.com \
      --port 4444 \
      --bindDN "cn=Directory Manager" \
      --bindPassword password \
      --trustAll \
      --no-prompt

• Platform Integration

  When setting up a directory server for use with other ForgeRock Identity Platform™ component products, you can use available setup profiles to greatly simplify initial configuration.

  For details, see "Using Directory Server Setup Profiles" in the Installation Guide.

  In addition, you can use profiles in embedded servers. For details, see "To Set Up an Embedded Server" in the Developer's Guide.

• Replication

  When configuring a replication server on a multi-homed system with multiple IP addresses, you can now specify which listen addresses to use.

  Set the property, listen-address, as shown in "Choosing the Listen Address for Replication" in the Administration Guide.

• Support

  The DS support extract command, supportextract, now ships with DS server software, making it easier to capture troubleshooting information.

  The command works on all supported platforms.

  For details, see "supportextract — extract support data" in the Reference.

• No additional improvements in this release.

• OPENDJ-7073: PKCS#11 key managers and trust managers now support non-default types. The default type is PKCS11.

• There were no product improvements in this release, only bug fixes.

• OPENDJ-5600: The supportextract tool should capture stack traces with jcmd

• OPENDJ-5960: The supportextract tool should gather basic changelogDb information

• OPENDJ-6163: The supportextract tool needs to gather archived-configs

• OPENDJ-6422: Make the supportextract tool compliant with JVM unified logging framework

• OPENDJ-6830: The supportextract tool should capture stack traces in server.out with SIGQUIT

• OPENDJ-6929: Support storing ads-certificate key-pair and other instance public keys in an HSM

• OPENDJ-6930: Increase interoperability with HSMs when protecting and distributing symmetric keys

• OPENDJ-6125: The supportextract tool needs to gather the rootUser and monitorUser ldif files

• OPENDJ-6128: The supportextract tool needs to gather Profile and Data Information

This release of Directory Services software includes the following enhancement:

• Tools Improvements

  All setup command profiles now allow you to set the domain or the base DN. For details, see "Using Directory Server Setup Profiles" in the Installation Guide.

This release of Directory Services software includes the following enhancements:

• DevOps

  Administrative tasks affecting directory server backends no longer modify the server configuration.

  This supports DevOps and other deployments that require an immutable configuration.

• Embedded Server

  Embedded directory servers now support both online and offline modes for importing LDIF and rebuilding indexes.

• Examples

  The server software now includes an example password storage scheme extension.

  For details, unzip the file /path/to/opendj/example-pwdscheme.zip and see the README file inside.

• Indexing

  The debugsearchindex attribute, used for investigating how searches are indexed, now holds JSON values that are significantly easier to read.

  For examples, see "Clarifying Which Indexes Are Used by a Search" in the Administration Guide.

• Java Support

  DS software now supports Java 8 and Java 11.

• LDAP Support

  DS servers now support the experimental LDAP Relax Rules control, as described in The LDAP Relax Rules Control (Internet-Draft).

• Logging

  • DS servers now maintain a filtered JSON LDAP access log in addition to the primary (unfiltered) access log.

    This log includes messages of interest to developers and administrators. For details, see "To Configure Filtered JSON LDAP Access Logs" in the Administration Guide.

  • Common Audit logging now supports logging to a PostgreSQL.

    For details, see "Configuring JDBC Access Logs" in the Administration Guide.

• Monitoring

  The monitoring dashboard samples now show the number of available DS servers.

• Password Management

  DS servers now support using proxied authorization with the LDAP password modify extended operation.

• Replication

  • DS servers now support strings as replication group IDs.

    For an example, see "Replication Groups" in the Administration Guide.

  • Standalone replication servers now support querying cn=changelog.

  • DS servers now provide a command to debug issues with the file-based changelog database, "changelogstat — debug changelog and changenumber files" in the Reference.

• REST to LDAP

  REST to LDAP now supports returning null-value fields in JSON resources.

  To enable this feature, set return-null-for-missing-properties:true for a Rest2ldap endpoint or "returnNullForMissingProperties": true in the REST to LDAP Gateway configuration file, rest2ldap.json.

  By default, a REST to LDAP mapping omits JSON fields for LDAP attributes that have no values. For example, the following entry is missing a value for the optional description:

       dn: uid=bjensen,ou=people,dc=example,dc=com
       objectClass: person
       uid: bjensen
       cn: Babs Jensen
       sn: Jensen
      

  A REST to LDAP mapping which maps the uid, cn, sn, and description attributes could return the following JSON:

  {
       "id": "bjensen",
       "fullName": "Babs Jensen",
       "familyName": "Jensen"
       }

  With the setting enabled, the mapping returns a JSON resource with a "description" field:

  {
       "id": "bjensen",
       "fullName": "Babs Jensen",
       "familyName": "Jensen",
       "description": null
       }

• Security

  • DS servers no longer overwrite a destination server's secret keys when configuring replication.

    As a result, you no longer need to configure replication before configuring data confidentiality, or before configuring an encrypted password storage scheme such as 3DES, AES, or Blowfish.

  • DS fingerprint certificate mappers now support SHA-256 as a fingerprint algorithm.

• Tools

  • The status command has been rewritten.

    For details, see "Important Changes to Existing Functionality".

  • The manage-account command now supports the following additional subcommands:

    • clear-account-expiration-time

    • clear-authentication-failure-times

    • clear-grace-login-use-times

    • clear-last-login-time

    • clear-password-changed-by-required-time

    • clear-password-changed-time

    • clear-password-expiration-warned-time

    • clear-password-history

    • clear-password-is-reset

    • set-account-expiration-time

    • set-authentication-failure-times

    • set-grace-login-use-times

    • set-last-login-time

    • set-password-changed-by-required-time

    • set-password-changed-time

    • set-password-expiration-warned-time

    • set-password-is-reset

    In addition, the actions can be performed over LDAP independently of the command by using the LDAP Password Policy State extended operation with OID 1.3.6.1.4.1.26027.1.6.1. DS servers implement a class for this operation. See the Javadoc for PasswordPolicyStateExtendedOperation.

  • DS command-line tools now have options to specify the keystore or truststore type when securing connections and using client authentication or authenticating the server.

    For details about the options available with each command, see "Tools Reference" in the Reference.

  • The DS ldapmodify and ldappasswordmodify commands now report password policy error codes when applicable.

  • Templates for the makeldif command now support a <DateTime> tag to generate timestamp values in LDIF attributes.

    For details, see "makeldif.template — template file for the makeldif command" in the Reference.

• Upgrade

  You can now upgrade mutable DS server data after upgrading the immutable binary files and configuration. Use the --dataOnly option with the upgrade command.

  This improvement is available when upgrading from DS 6.0.0 or later releases.

• Linux 2.6 and later

• Microsoft Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2016

• Oracle Solaris 10, 11 (SPARC, x64)

Before adjusting settings, determine the following container constraints:

• The number of CPU core hardware threads dedicated to the containerized system, which is usually twice the number of CPU cores

• The amount of RAM dedicated to the containerized system

When running DS servers in containers such as Docker, adjust the following settings:

• num-request-handlers

  Recommendation: Set this either to 2 or to 1/4 of the number of core hardware threads, whichever is larger.

• num-worker-threads

  Recommendation: Set this either to 4 or to 5/8 of the number of core hardware threads, whichever is larger.

• db-num-cleaner-threads

  Recommendation: Set this either to 2 or to 1/4 of the number of core hardware threads, whichever is larger.

• num-update-replay-threads

  Recommendation: Set this either to 4 or to 1/2 of the number of core hardware threads, whichever is larger.

• -Xmx (Java setting limiting maximum heap size)

  To use the option, edit the config/java.properties file and restart the server.

  For example, consider a container limited to 8 GB RAM. The following setting limits the maximum heap size to 8 GB when starting the directory server:

  start-ds.java-args=-server -Xmx8G
              

• No changes in this release.

• No changes in this release.

• No changes in this release.

• No changes in this release.

• No changes in this release.

• Property je-backend-shared-cache-enabled Changes Default Value After Upgrade from 6.5.0 to 6.5.1

  There is an issue when running an upgrade from DS 6.5.0 to 6.5.1. If you did not set the je-backend-shared-cache-enabled property and accepted the default value of TRUE prior to the upgrade, the value changes AFTER upgrade to FALSE. You may have to reset this value to TRUE for your deployments.

  If you set the je-backend-shared-cache-enabled property prior to upgrade to either TRUE or FALSE, the value does not change after upgrade.

Take the following changes into account when upgrading to Directory Services 6.5. These changes will have an impact on existing deployments. Adjust existing scripts and clients accordingly:

• The status command has been rewritten, with the following notable changes:

  • The command is no longer interactive.

    You must supply the required options when invoking the status command.

  • The command now has an --offline option.

    When you run status --offline on a running server, the command only displays a portion of the available information.

  • You can now run the command against a remote DS server version 6 or later.

  • The output shows more information than before.

• The dsreplication status command no longer shows metrics for M.C. (missing changes) and A.O.M.C. (age of oldest missing change). Instead, it shows the replication delay.

  For DS 6 and later servers that expose a replication delay metric, the command shows the delay value. For DS 5.5 and earlier servers, the command shows N/A.

• The db/admin backend has been renamed db/adminRoot.

• The global server configuration property, reject-unauthenticated-requests, a boolean, has been removed and replaced with the property, unauthenticated-requests-policy.

  The new property can be set to the following values:

  reject

  Same behavior as reject-unauthenticated-requests:true

  allow

  Same behavior as reject-unauthenticated-requests:false

  allow-discovery

  Like reject, but allows unauthenticated base object searches of the root DSE

• The server-side (plugin) Java API is continuing to evolve, as noted in "Release Levels and Interface Stability".

  Server plugins written against this API will have to be adapted and recompiled to work with this version. For Java API reference documentation, see the Javadoc.

• The example server plugin described in "Writing a Server Plugin" in the Developer's Guide unpacks LDAP schema files into a db/schema directory. This is the correct schema file location for new DS servers since the 6.0 release.

  When you upgrade a server from version 5.5.x or earlier, however, schema files remain in the config/schema directory. As a result, when using the example plugin with the upgraded server, you must manually move schema files from the db/schema directory to the config/schema directory.

• The proxy backend configuration property service-discovery-mechanism has been renamed shard.

• The encode-password command now displays the encoded password without additional characters.

  In other words, the output is now {scheme}encoded-password rather than Encoded Password: "{scheme}encoded-password".

• No changes in this release.

• No changes in this release.

• No changes in this release.

• Support for the Solaris operating system is deprecated and will be discontinued in a future release.

• The backup, restore, and dsreplication commands are deprecated in this release and will be replaced with equivalent functionality in a future release.

• There are no new deprecated features in DS 6.5.1, other than those identified in DS 6.5.0.

• All dsreplication subcommands are deprecated. Their names, meanings, and outputs are likely to change in a future release. This includes the following subcommands:

  • dsreplication configure

  • dsreplication initialize

  • dsreplication initialize-all

  • dsreplication post-external-initialization

  • dsreplication pre-external-initialization

  • dsreplication purge-historical

  • dsreplication reset-change-number

  • dsreplication resume

  • dsreplication status

  • dsreplication suspend

  • dsreplication unconfigure

• The setup command may be replaced by a simpler implementation in a future release.

• The HTTP monitoring endpoint, /admin/monitor, has been deprecated.

  Use /metrics/api or /metrics/prometheus instead.

• The following metrics are deprecated:

  • ds-mon-approx-oldest-change-not-synchronized (LDAP)

  • ds-mon-approximate-delay (LDAP)

  • ds-mon-missing-changes (LDAP)

  • ds_replication_changelog_connected_replicas_approx_oldest_change_not_synchronized_seconds (Prometheus)

  • ds_replication_changelog_connected_replicas_approximate_delay_seconds (Prometheus)

  • ds_replication_changelog_connected_replicas_missing_changes (Prometheus)

  Note

  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 reflected in the dsreplication status output and the values of the deprecated metrics described above.

  The delay is calculated correctly again once all servers in the topology are upgraded to at least version 6.5, or when the offline the server comes back online and has seen a change to directory data.

  Monitor replication delay instead of using the deprecated metrics. For details, see "Monitoring Replication Delay Over LDAP" in the Administration Guide or "Monitoring Replication Delay Over HTTP" in the Administration Guide.

• No changes in this release.

• No changes in this release.

• There are no removed features in DS 6.5.4, other than those identified in DS 6.5.0.

• There are no removed features in DS 6.5.3, other than those identified in DS 6.5.0.

• There are no removed features in DS 6.5.2, other than those identified in DS 6.5.0.

• There are no removed features in DS 6.5.1, other than those identified in DS 6.5.0.

• The manage-account get-password-history subcommand has been removed due to security concerns.

• OPENDJ-8698: DS should write config archive files in a crash consistent way

• OPENDJ-8845: Bad encoding of PersistentSearch's changeType of the EntryChangeNotificationResponseControl

• OPENDJ-7970: Ensure that DS is crash resilient for all runtime file changes

• OPENDJ-7761: DS sporadically hangs while reconnecting to an RS

• OPENDJ-7653: replication issue in the cloud after ldapadd

• OPENDJ-6349: "RuntimeException: Should never happen" in HttpClientConnection

• OPENDJ-5927: Server stuck on a DS trying to reconnect to an RS

• OPENDJ-6992: Persistent search from IDM is blocking worker threads.

• OPENDJ-7450: The startswith (sw) operator on indexed JSON attribute is slow

• OPENDJ-7481: JSON logs do not contain proxy auth DN

• OPENDJ-7655: Replaying multiple MODIFYDN operations is very slow

• OPENDJ-7699: Supportextract throws NoSuchElementException when the server.pid file is empty

• OPENDJ-7737: ConfigurationFramework#initialize0 changes the class loader without clearing the map of registered jar files

• OPENDJ-7818: Package based upgrade does not support instances running as non-root

• OPENDJ-7851: Supportextract tool: clobbers the server.out filehandle when kill -3 is used.

• OPENDJ-8028: Prometheus monitoring doesn't work with Telegraf

• CMON-109: Prometheus metrics contains more than one HELP metric line for the same metric

• OPENDJ-4058: IDM Account Status notification handler doesn't look for certificates correctly

• OPENDJ-5439: LeastRequestsStrategy should distribute load randomly when idle

• OPENDJ-5851: ACI: getEffectiveRights with authz do not print out acl rights

• OPENDJ-6309: Search operation on whole tree skips nodes if there are DNs without backends in the directory information tree (DIT)

• OPENDJ-6377: Replication replay: issues with ReplaySynchronizer

• OPENDJ-6498: Profile creation stores AM cts and config global aci's in base64 format

• OPENDJ-6711: Replication status reports The provided value "5277383431" could not be parsed as an integer.

• OPENDJ-6812: Client tools fail in offline mode when Account Status Notification Handlers are used

• OPENDJ-6910: Supportextract --maxLogFiles gathers logs but not the latest logs

• OPENDJ-6970: Tamil locales cause illegal matchingRules values

• OPENDJ-6994: Strict-format-country-string does not affect the server

• OPENDJ-7014: Some operational attributes are not replicated when a restore --dry-run is used against an online server

• OPENDJ-7016: Status command outputs malformed JSON in script friendly mode

• OPENDJ-7020: Rebuild-index offline ignores rebuild-index.offline.java-args

• OPENDJ-7031: VLVIndex are incorrectly rebuilt by rebuild-index

• OPENDJ-7115: DS does not start when deployed with ISTIO side car container in the GCP K8s cloud

• OPENDJ-7176: Filters with malformed attribute descriptions cannot be parsed

• OPENDJ-7232: StackOverflowError in Tomcat logs when using external DS

• OPENDJ-7286: Changelog searches can start with incorrect cursors

• OPENDJ-7414: AM: Persistent search with changesOnly gets cancelled by a request timeout

• OPENDJ-5600: The supportextract tool should capture stack traces with jcmd

• OPENDJ-5895: Unable to rebuild indexes when the Error Log Handler is assigned to a password policy

• OPENDJ-5960: The supportextract tool should gather basic changelogDb information

• OPENDJ-6163: The supportextract tool needs to gather archived-configs

• OPENDJ-6240: DS not honoring per user resource limits when processing RESTful operation requests

• OPENDJ-6371: The supportextract tool generates data but returns 1 instead of 0 on Windows

• OPENDJ-6394: Update forgerock-commons for 6.5.3

• OPENDJ-6422: Make the supportextract tool compliant with JVM unified logging framework

• OPENDJ-6464: IsMemberOfVirtualAttributeProvider does not process subordinate nested groups

• OPENDJ-6474: REST: some requests fails when stressing embedded http endpoint with Gatling

• OPENDJ-6512: Problems when work queue fills

• OPENDJ-6521: setup checks admin port despite options --skipPortCheck --doNotStart

• OPENDJ-6527: server does not return password policy responses with only warnings

• OPENDJ-6540: The supportextract tool hangs when loggers are configured to use /dev/stdout

• OPENDJ-6557: IDM Password Sync plugin induces 100% CPU in Apache Http Components when used with JDK 11

• OPENDJ-6675: The supportextract tool cannot collect gc files when there are dots in the path

• OPENDJ-6695: Heap slowly fills with DomainDBCursors

• OPENDJ-6708: The supportextract tool fails with an error parsing json

• OPENDJ-6733: SMTP handler sends incorrect email when account status is modified by manually updating ds-pwp-account-disabled attribute

• OPENDJ-6781: example-plugin fails to build on 6.5 branch

• OPENDJ-6778: Proxy server mishandles abandon requests

• OPENDJ-6787: Changelog searches are extremely slow if any cursors are exhausted

• OPENDJ-6820: dsconfig "-w -" option doesn't prompt for password

• OPENDJ-6822: Reduce number of expensive seeks in BlockLogReader

• OPENDJ-6830: The supportextract tool should capture stack traces in server.out with SIGQUIT

• OPENDJ-6892: Incorrect units for two updates metrics

• OPENDJ-6929: Support storing ads-certificate key-pair and other instance public keys in an HSM

• OPENDJ-6930: Increase interoperability with HSMs when protecting and distributing symmetric keys

• OPENDJ-5972: bin/status command fails when using a french locale

• OPENDJ-6125: supportextract tool needs to gather the rootUser and monitorUser ldif files

• OPENDJ-6128: supportextract tool needs to gather Profile and Data Information

• OPENDJ-6170: supportextract tool misses rotated or non-standard GC log files

• OPENDJ-6173: cn=monitor memory pool stats do not get updated properly over time

• OPENDJ-6196: HTTP connection handler continues to listen to 0.0.0.0 after setting listen-address

• OPENDJ-6217: NPE when running supportextract tool on upgraded instance

• OPENDJ-6222: SMTP messages are sometimes not encoded with the correct charset

• OPENDJ-6248: NPE when running supportextract without monitoring user configured

• OPENDJ-6235: Stale ds-sync-hist attribute values reappear in the entry after replication is unconfigured

• OPENDJ-5423: Incorrectly reported missing parent entries cause import-ldif and index rebuilds to fail

• OPENDJ-5584: Server does not validate sum of memory used by JE backend caches in all cases

• OPENDJ-5611: Change number indexing can lag behind replication under extreme load

• OPENDJ-5675: JDK11: supportextract tool cannot find jstack command

• OPENDJ-5726: Proxy distribution has trouble scaling writes to 3 shards

• OPENDJ-5727: Add optional base DN for each profile

• OPENDJ-5793: Replication on windows: ChangelogException while adding entries

• OPENDJ-5794: JE db-cache-size settings conflicts with shared cache

• OPENDJ-5801: ldap operation fails with "49 Invalid Credentials" when bindDN of 'cn=Directory Manager' is supplied in a properties file

• OPENDJ-5843: Rebuild-index failed with ConfigException on db-cache-size

• OPENDJ-5955: Missing version fallback feature for profiles

• OPENDJ-5977: Can not use custom base dn with cts profile because organization unit is forced

• OPENDJ-5979: Server does not validate sum of memory used by JE backend caches after upgrade

• OPENDJ-6039: AM Config Store Profile doesn't have enough access in ProductionMode when upgrading AM

• OPENDJ-6089: TelephoneNumber syntax in DN creates an incorrect entry DN value

• OPENDJ-5406: Duplicate entry DNs if entry is deleted and then added during export-ldif or dsreplication initialize

• OPENDJ-5140: PersistentSearch heap usage grows

• OPENDJ-5553: Rest2Ldap cannot connect to TLSv1.2 servers

• OPENDJ-5496: DS fails to reconnect to an RS, disconnecting in handshake phase, after system restart

• OPENDJ-5594: StackOverflowError with groupOfURLs when isMemberOf is requested

• OPENDJ-4589: dsconfig --offline is not case-insensitive

• OPENDJ-4325: Changelog searches requesting changelogCookie are very slow

• OPENDJ-3341: REST to LDAP gateway: HTTP response for API description is empty

• OPENDJ-5210: Possible memory-leak if request received while bind in progress

• OPENDJ-3153: REST to LDAP gateway: changing password fails when using proxied authorization

• OPENDJ-5272: "idle-time-limit" global configuration property has no effect

• OPENDJ-5137: Reading compressed or encrypted entries fails to close the InflaterInputStream

• OPENDJ-5606: Upgrade to DS 6.0 fails if multiple filesystems are involved

• OPENDJ-4625: Changelog range searches miss entries

• OPENDJ-2356: verify-index displays an inappropriate error message when run in online mode

• OPENDJ-4229: status command with keystore options throws NullPointerException

• OPENDJ-4852: Backup with --backupAll misses a few backends

• OPENDJ-4881: Updates via Rest2ldap fail if record does not contain the necessary object class

• OPENDJ-5115: ldappasswordmodify fails, NPE in PasswordPolicyState updatePasswordHistory

• OPENDJ-4967: Rest2ldap UndeliverableException occurs when a referenced entity cannot be fetched

• OPENDJ-5558: SDK: LdapUrl is not IPv6 clean

• OPENDJ-5481: ERR_OPERATION_NOT_FOUND_IN_PENDING message used twice in different contexts

• OPENDJ-3343: Invalid Conflict resolution on Add sequence when Parent & Child are added on different replica

• OPENDJ-4947: SASL DIGEST-MD5: bind request failed with protocol error

• OPENDJ-5582: LdapClientSocket connection leaked when handshake fails

• OPENDJ-5293: Proxy: Replication Service Discovery Mechanism logs WARNING

• OPENDJ-3480: Updating schema backend properties while it is enabled leaves schema backend in broken state

• No changes in this release.

• No changes in this release.

• There are no limitations in DS 6.5.4, other than those identified in DS 6.5.0.

• There are no limitations in DS 6.5.3, other than those identified in DS 6.5.0.

• There are no limitations in DS 6.5.2, other than those identified in DS 6.5.0.

• There are no limitations in DS 6.5.1, other than those identified in DS 6.5.0.

DS 6.5.0 has the following limitations:

• Configuring a server with both local backends and proxy backends is not supported.

  As described in "Configuring Privileges and Access Control" in the Administration Guide, access control models for directory servers and proxy servers cannot function at the same time in the same server.

• DS servers provide full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2.

• Directory servers store passwords prefixed with the storage scheme in braces, as in {scheme}. For details, see "Configuring Password Storage" in the Administration Guide.

  To prevent users from effectively attempting to choose their own password storage scheme, directory servers do not support passwords that strictly match this format. Specifically, directory servers do not support passwords that match {string}*.

  Requests to update userPassword values with such passwords fail with result code 19 (Constraint Violation) and an additional message indicating that passwords may not be provided in pre-encoded form.

• When you configure account lockout as part of password policy, DS directory servers lock an account after the specified number of consecutive authentication failures. Account lockout is not transactional across a replication topology, however. Global account lockout occurs as soon as the authentication failure times have been replicated.

• When configuring replication between servers with different versions, use the appropriate dsreplication command:

  • When adding a new server to a replication topology with 2.6.x servers, use the dsreplication command installed with a 2.6 server.

  • When adding a new server to a replication topology with 3.x and later servers, use the dsreplication command installed with a new server.

  • After adding servers, use the dsreplication command installed with a new server.

• The policy-based access control handler used in proxy servers:

  • Does not support the Get Effective Rights control.

  • Does not check the modify-acl privilege when global access control policies are changed. The config-write privilege is sufficient to change global access control policies.

  • Does not send alert notifications when global access control policies change.

• When using ACIs or collective attributes with the proxy server data distribution feature, the ACI and entries having collective attribute values must be located at or above the partition-base-dn. When changing this data, make the change behind the proxy to one directory server replica in each shard. Your changes are not replicated outside the shard.

  The proxy server data distribution feature does not currently support the following:

  • Importing distributed data with the import-ldif command.

  • Changes to the number of partitions after data has been deployed.

  • Modify DN operations to distributed entries.

  • Updates to entries at or above the partition-base-dn.

  • Virtual static groups.

  • Data distribution does not support these virtual attributes:

    member

    uniqueMember

    The isMemberOf virtual attribute works as expected as long as you replicate the group entries on every shard.

  • Data distribution does not support these LDAP controls:

    Server-Side Sort controls: 1.2.840.113556.1.4.473, 1.2.840.113556.1.4.474

    Simple Paged Results control: 1.2.840.113556.1.4.319

    Virtual List View controls: 2.16.840.1.113730.3.4.9, 2.16.840.1.113730.3.4.10

• The Password Policy control (OID: 1.3.6.1.4.1.42.2.27.8.5.1) is supported for add, bind, and modify operations. It is not supported for compare, delete, search and modify DN operations.

• REST to LDAP does not support modify RDN operations.

• Prevent antivirus and intrusion detection systems from interfering with DS software.

  Before using DS software with antivirus or intrusion detection software, consider the following potential problems:

  Interference with normal file access

  Antivirus and intrusion detection systems that perform virus scanning, sweep scanning, or deep file inspection are not compatible with DS file access, particularly database file access.

  Antivirus and intrusion detection software can interfere with the normal process of opening and closing database working files. They may incorrectly mark such files as suspect to infection due to normal database processing, which involves opening and closing files in line with the database's internal logic.

  Prevent antivirus and intrusion detection systems from scanning database and changelog database files.

  At minimum, configure antivirus software to whitelist the DS server database files. By default, exclude the following file system directories from virus scanning:

  • /path/to/opendj/changelogDb/ (if replication is enabled)

    Prevent the antivirus software from scanning these changelog database files.

  • /path/to/opendj/db/

    Prevent the antivirus software from scanning database files, especially *.jdb files.

  Port blocking

  Antivirus and intrusion detection software can block ports that DS uses to provide directory services.

  Make sure that your software does not block the ports that DS software uses. For details, see "Limiting System and Administrative Access" in the Security Guide.

  Negative performance impact

  Antivirus software consumes system resources, reducing resources available to other services including DS servers.

  Running antivirus software can therefore have a significant negative impact on DS server performance. Make sure that you test and account for the performance impact of running antivirus software before deploying DS software on the same systems.

• REST to LDAP query filters do not work with properties of subtypes.

  For example, the default example configuration describes a user type, and a POSIX user type that inherits from the user type. If your query filter is based on a POSIX user type property that is not a property of the user type, such as loginShell or gidNumber, the filter always evaluates to false, and the query returns nothing.

• When applying a Common REST patch operation, described in "Patching Resources" in the Developer's Guide, to a Json syntax attribute, you cannot patch individual fields of the JSON object. You must change the entire JSON object instead.

  As a workaround, you can perform an update of the entire object, changing only the desired fields in your copy.

• When the global server property invalid-attribute-syntax-behavior is set to accept or warn, a search on group membership using a value with invalid syntax returns nothing.

• Due to a Java issue on Windows systems (JDK-8057894), when configuring DS directory servers with data confidentiality enabled you might see an error message containing the following text:

  Unexpected CryptoAPI failure generating seed

  If this happens, try running the command again.

• OPENDJ-8842: Proxy DS does not cancel psearch to Backend DS if psearch is cancelled

• OPENDJ-8460: Deploying DS6.5.5+JDK11 causes continuous hostname resolution errors in pods with DS6.5.5+JDK8

• OPENDJ-8137: LDIF backend silently rejects entries that fail schema validation

• OPENDJ-8089: rest2ldap gateway returns string instead of boolean

• OPENDJ-7942: The server ignores critical VLV request controls when falling back to an unindexed search

• OPENDJ-7919: A search for modifyTimestamp>=00000101000000Z results in a YEAR error and disconnect

• OPENDJ-7654: DS is sometimes unable to connect to RS after full gc

• OPENDJ-7643: Log that is supposedly generated from dsreplication operation is empty or does not exist

• OPENDJ-7640: Supportextract doesn't collect all security store info if both key manager and trust manager use the same store file

• OPENDJ-7516: External cn=changelog is not updated while replication initialization is in progress

• OPENDJ-7286: Changelog searches can start with incorrect cursors

• OPENDJ-7219: PreParseAddOperation cannot remove attributes

• OPENDJ-7197: Health Status returns OK however server is having JVM issues and cannot serve requests

• OPENDJ-6992: Persistent search from IDM is blocking worker threads.

• OPENDJ-6787: Changelog searches are extremely slow if any cursors are exhausted

• OPENDJ-6579: Schema is not populated to remote instances if added before enabling replication

• OPENDJ-6468: Some prometheus metrics are labeled as gauge, but seem to be counters

• OPENDJ-6465: same value for 'baseDn' profile property can be specified during setup

• OPENDJ-6380: Warning message for duplicate objectlass schema definition is misleading

• OPENDJ-6149: The Global Access Control Policy option within the dsconfig tool is misleading as is the error message returned

• OPENDJ-6022: PTA to Active Directory returns more than one entry when only one exists

• OPENDJ-5964: Replication: DS fails to fail-back to its local RS

• OPENDJ-5956: Data discrepancy between servers if the same attribute has extra spaces in RDN

• OPENDJ-5650: supportextract: Some Linux distros need htop instead of top -H

• OPENDJ-5201: Tools may prompt to trust certificate multiple times for different reasons