opendj | Apply Open Source principles to the Dance Floor | Animation library

I don't believe it's missing the certificate file. It's most likely due to a change of behavior of JDNI with an update of JDK8. See https://stackoverflow.com/a/58930712/738708.

The first error with Status is due to changes in JDK 8 where certificates subject name much match the hostname you are trying to connect to.

The second part of the question is not an error. It's expected. Your first query is requesting no attributes (trailing argument '1.1' means to return no attributes). The second query is requesting attributes that do not exist in the rootDSE for OpenDJ 3.0. These attributes were added to ForgeRock Directory Service version 6.5.0.

Have you tried as below

look at your docker ps command, you do not publish any ports

add this to your docker run command:

This can be solved with global values which allow values in the parent chart to override (or supply unspecified) values in the child subcharts.

From the Helm docs on Subcharts and Global Values:

1. A subchart is considered “stand-alone”, which means a subchart can never explicitly depend on its parent chart.
2. For that reason, a subchart cannot access the values of its parent.
3. A parent chart can override values for subcharts.
4. Helm has a concept of global values that can be accessed by all charts.

(At first I didn't think to search for "helm subchart" but once I did an Internet search for that term, this was the first or second result)

Here's a minimal example that solves your issue:

It looks like the Novell LDIF reader is strictly accepting LDIF version 1 from RFC 2849. The first line should contain version: 1 OpenDJ does support adding schema over LDAP, it must be a change of cn=schema, adding values to the attributeTypes and objectClasses attributes.

Extending schema over LDAP with OpenDJ and ForgeRock Directory Services is fully documented on https://backstage.forgerock.com/docs/ds. It is slightly different from openLDAP syntax and method: it’s a modify operation of the cn=schema suffix adding values of the attributeTypes and objectClasses attributes.

Here’s the above example ready to be added over LDAP to OpenDJ, ForgeRock Directory Services, SunDSEE...

That is correct, there should be no change to the applications (since the interface is standard LDAPv3).

If your OpenDS service is replicated, you can upgrade one server after another, with zero downtime for the overall service.

When upgrading from 2.6, you will probably need to upgrade the Java runtime as well, since DS 6.5 requires Java 8 (and also supports 11).

So, stop a server, backup the whole server, unzip DS 6.5, upgrade Java to 8+, run upgrade, start-ds.

You might want to test the upgrade process on a dev environment. If you don’t have a dev env yet, you can create one by just copying the whole OpenDJ 2.6.4 directory and databases to a different location or another server.

ForgeRock Directory Services 6.5 is the continuation of OpenDJ by ForgeRock as a private branch (before that 99.95% of the contributions to OpenDJ were done by ForgeRock).

You can get a feel of the amount of changes between version 3 and version 6.5 by reading the release notes of all the ForgeRock releases. It's quite significant in 3 years.