https://bugs.openldap.org/show_bug.cgi?id=9269
--- Comment #2 from Konstantin Andreev <[email protected]> --- > Certainly the "hidden" option was never meant to be used in a glued DB. Formally, this intention/limitation is not documented, so I expect "hidden" option works as described for subordinate databases too: "A database that is hidden will never be selected to answer any queries". The "database" here is the database from config pov, not a "naming context" from the user pov, not to mention subordinate databases may be advertised as independent naming contexts/dits. I see this as conflict between documentation and reality, that needs resolution. If you just document the limitation, it might be a resolution too. > What is the use case for this configuration? I am interested in implementing a custom feature on openldap, that, in this context, similar to 'hidden' option. So, the 'hidden' option implemented properly would ease me an efforts. If not, I am on my own. But wait, ... what is the use case for 'hidden' option for standalone databases? -- You are receiving this mail because: You are on the CC list for the issue.
