History of Previous Releases

Kubernetes deployment - From v9.1 on, DirX Directory is also delivered in form of container images. The release contains also a Kubernetes example project which could be used to evaluate and experiment with the container images. For details, please check the new DirX Directory Containerization document.

Code signing - verification of binaries: see Section 2.6 for details.

License control - verification of DirX Directory license: see Section 1.2.8 for details.

Time-based one-time password two-factor authentication (TOTP 2FA) for DirX Directory users: see chapter "14.8 Using Two-Factor Authentication (2FA)" in DirX Directory Administration Guide for details.
Important note for shadowing configurations:
TOTP 2FA should only be configured for a user, if all servers in a shadowing configuration support it (all servers are already updated to V9.1 version).

New dirxcp command "verify_abbr" was introduced to check the installed abbreviation files against the schema stored in the DSA. In connection with that new feature, the dirxabbr file has been synchronized to the default schema. Abbreviations that are not part of the default schema have been commented out and moved into a separate section labelled as "Historical Abbreviations". To reuse them if needed, move the selected abbreviations from this section to an application- specific dirxabbr-ext file and uncomment them there. See the section "Abbreviation Files" in the DirX Directory Administration Reference for details.

New DSE type checks have been introduced in dbamverify, which upon detection of errors previously unseen, will block any new backups to be made. Therefore it is highly recommended to take a backup right before switching to the new version.

Partial support for 4 bytes UTF-8 characters (emojis) in attributes with Directory String syntax was added. For details on limitations see Section 5.4.1 (DirX server limitations)

Optimized import-dbconfig Tcl procedure for attribute index configuration
The old version of this procedure processed all lines in DirXDBConfig.out index configuration file sequentially and issued one 'db attrconfig' command per 'attributeIndex: …​' line, creating all requested index types for this attribute. In the new version it combines up to 200 'attributeIndex: …​' lines for one index type (e.g: INITIAL, …​) into one single 'db attrconfig' command. This new approach is much faster, than the old method.

Software Bill of Materials file (DirX-Directory-sbom.json) containing information about delivered components and their versions was added to the DirX Directoty installation package.

LDAPServer now supports the 'SecurityLevel' feature of OpenSSL.
(see: https://www.openssl.org/docs, search for set_security_level for details) Because of this the LdapSSLConfiguration subentry was extended with 2 new attributes: ldapSecLevelA and ldapSecLevelB. For details about these new attributes please refer to the Syntaxes and Attributes Manual, chapter 3.1.15 Attributes for LDAP Server SSL Configuration.

Default schema has been extended with 3 new attribute types: dmdName, pseudonym and organizationIdentifier. For details about these new attributes please refer to the Syntaxes and Attributes Manual, chapter 3.1.2 X.500 User Application Attributes, Names in General.

dirxbackup now can generate a full LDIF dump or an LDIF dump of a specified subtree from a binary backup. For details, please check the documentation of dirxbackup’s -L command line argument in the Administration reference.

ldif_dump and create_total_ldif now can dump a subtree as well. Both commands were extended with an optional subtree parameter to be able to define the starting point of the LDIF dump in the tree.

dirxbackup’s saving functionality was extended to automatically verify the generated binary backups. To preserve the previous behavior and only create the backup without automatic verification, the -n switch can be used.

Binary backup headers were extended to contain verification information. From this version on, dbamverify and dirxbackup will write the result and some metadata of the executed verification to the backup file’s header. This verification information is checked by dirxbackup’s restore operation. If a backup was not completely verified or contains errors, then loading will be rejected.

A new server, dirxhttp was introduced to the DirX Directory service. It makes possible to access the DIT using the HTTP protocol with a custom JSON schema. An interactive API documentation can be found at https://<server_ip>:9443/dxd/ldap/v1/doc

New paging memory optimization was introduced. This optimized paging memory handling, aims to reduce the size of the paging memory context during paged search operations compared to the previous version especially in case of filters with a huge number of elements. The optimization can be disabled by setting the DIRX_PAGING_MEMORY_OPTIMIZATION environment variable to zero.

SchemaChangelog: Provides information of all schema changes ever made since the DSA was first started with the currently running DB. The log information is stored in the hidden logfile <DIRX_INST_PATH>/server/log/.schema_changes.txt The logfile will only be reset in case of a successful dbamboot or dirxbackup -R.

dirxadm RPC operations targeting the DSA are now logged in the DSA audit files. Because of this new feature the RPC interface between dirxadm and DSA has been extended, so it is not possible to use an older version of the dirxadm tool together with DirX V9.0.

new log collector scripts available for both Windows/Linux versions to ease symptom collection in case of an incident. The scripts (dxd_diag.bat/dxd_diag.sh) can be found under tools\dxd_diag folder. See readme file in that folder for more details.