Issue 7663 - Add 'namingContexts' to backend entry below cn=Backends,cn=Monitor
Summary: Add 'namingContexts' to backend entry below cn=Backends,cn=Monitor
Status: UNCONFIRMED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-13 11:09 UTC by Michael Ströder
Modified: 2020-03-20 17:32 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Michael Ströder 2013-08-13 11:09:34 UTC 
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.
Comment 1 Quanah Gibson-Mount 2020-03-20 17:32:25 UTC 
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 "".