An OEM customer is migrating from legacy Sun DSEE to OpenDJ
Customer currently relies on ldapsearch returning a list of all Naming Contexts, including sub-suffixes (used for domains)
OpenDJ does not work this way (you do not see sub-suffix as a namingcontexts because it is already provided as a namingcontexts from the base of the suffix.)
Customer would like OpenDJ to offer equivalent ldapsearch functionality
The OEM's business case for the change is that they cannot restrict their end customers from creating domains or follow some domain naming convention that they internally enforce,
For example: maindomain.com, northreg.maindomain.com, southreg.maindomain.com
They would expect to see a return of all the 3 domains as they are all unique entities.
Currently OpenDJ will only list maindomain.com which would be seen as a regression.
Another view, is that tools like ldapbrowser Jexplorer make use of namingcontexts when it tries to list what domains are being created and listed under the instance, and those are not working correctly as they don’t get the full list of the domains, and it is not possible to change those browsers to use the backend listing which is specific for OpenDJ.