A search for attributes in cn=config should return all attributes, including the ones the user didn't set and which uses their default value.
There are attributes, such as nsTLSAllowClientRenegotiation and allowWeakCipher, which are not returned in a search if the attribute was not set
389-ds-base-1.3.9.1-10.el7.x86_64 389-ds-base-1.4.1.10-1.module+el8dsrv+4575+0d8b81fc.x86_64
A search in cn=config should always return all attributes - including the ones that use their default value because they are not set by the user.
If we have a consistent behavior (all cn=config attributes incl. the ones with default values) are shown, then we could write a script that lists all attributes. We could use this list to identify what attributes are missing in the docs before a release, but also to identify attributes that have been removed.
I know that this wouldn't help us to create a full list of attributes in cn=config because some DNs don't exist by default or are dynamic (e. g. cn=<suffixDN>,cn=mapping tree,cn=config), but it would be better than nothing. :-)
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.3
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3804
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.