Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (79.219.109.139) Feature request: It would be quite handy if attribute 'namingContexts' would be available in backend entries in subtree cn=Backends,cn=Monitor. This would allow to quickly query the set of supported LDAPv3 ext. controls in attribute 'supportedControl' for a given naming context. Of course one can query the DB entry below cn=Databases,cn=Monitor and look at 'seeAlso' but that's extra amount of work without added value especially since 'seeAlso' is multi-valued also pointing to overlay entries. Alternative would be to add 'supportedControl' to entries below cn=Databases,cn=Monitor.
Curious: how does one handle the case where the database is rooted at "", and is specifically adding naming contexts in the frontend slapd process via the rootdse <file> directive? This is done to work around broken applications that can't handle a DB rooted at "".