Directory Servers have been used and continue to be used to store and retrieve identity information, including some data that is sensitive and should be protected. OpenDJ LDAP Directory Services, like many directory servers, has an extensive set of features to protect the data, from securing network connections and communications, authenticating users, to access controls and privileges… However, in the last few years, the way LDAP directory services have been deployed and managed has changed significantly, as they are moving to the “Cloud”. Already many of ForgeRock customers are deploying OpenDJ servers on Amazon or MS Azure, and the requirements for data confidentiality are increasing, especially as the file system and disk management are no longer under their control. For that reason, we’ve recently introduced a new feature in OpenDJ, giving the ability to administrators to encrypt all or part of the directory data before writing to disk.
The OpenDJ Data Confidentiality feature can be enabled on a per database backend basis to encrypt LDAP entries before being stored to disk. Optionally, indexes can also be protected, individually. An administrator may chose to protect all indexes, or only a few of them, those that contain data that should remain confidential, like cn (common name), sn (surname)… Additionally, the confidentiality of the replication logs can be enabled, and then it’s enabled for all changes of all database backends. Note that if data confidentiality is enabled on an equality index, this index can no longer be used for ordering, and thus for initial substring nor sorted requests.
Example of command to enable data confidentiality for the userRoot backend:
dsconfig set-backend-prop \
-h opendj.example.com -p 4444 \ -D "cn=Directory Manager" -w secret12 -n -X \ --backend-name userRoot --set confidentiality-enabled:true
Data confidentiality is a dynamic feature, and can be enabled, disabled without stopping the server. When enabling on a backend, only the updated or created entries will be encrypted. If there is existing data that need confidentiality, it is better to export and reimport the data. With indexes data confidentiality, the behaviour is different. When changing the data confidentiality on an index, you must rebuild the index before it can be used with search requests.
When enabling data confidentiality, you can select the cipher algorithm and the key length, and again this can be per database backend. The encryption key itself is generated on the server itself and securely distributed to all replicated servers through the replication of the Admin Backend (“cn=admin data”), and thus it’s never exposed to any administrator. Should a key get compromised, we provide a way to mark it so and generate a new key. Also, a backup of an encrypted database backend can be restored on any server with the same configuration, as long as the server still has its configuration and its Admin backend intact. Restoring such backend backup to fresh new server requires that it’s configured for replication first.
The Data Confidentiality feature can be tested with the OpenDJ nightly builds. It is also available to ForgeRock customers as part of our latest update of the ForgeRock Identity Platform.
I am recently playing with opendj. According to Forgerock, seems its Enterprise Binary cannot be used free in production without subscription fee.
But looks like I can build the source code myself and then use it free in production. Is this true ?
If yes, which branch I can use ? Master or release/3.0.0?
And what is the real software difference between the one I build myself than Forgerock enterprise binary? Any functional difference ?
Looking forward to see your answer.
Thanks in advance.
I believe you’ve also asked the same question on StackOverflow and it was already answered. But for the record, the answers are 1/ yes 2/ You should use master. The 3.0.0 release branch was used to build but will not evolve on the open source repository. 3/ There are no functional differences, the code is identical. However, ForgeRock enterprise binaries are fully qualified, heavily tested and supported so we can provide patches and security fixes to our customers. With any binary that you build yourself, you will be on your own, and will have to find and correct possible issues yourself.