Learn more about these different git repos.
Other Git URLs
In order to process site-linked GPOs, the GPO code needs to determine the site's DN (from which it can retrieve the relevant LDAP attributes). In order to construct a site's DN, the DN of the configuration container is required, which can be retrieved from the rootDSE entry's configurationNamingContext (configNC) attribute. Note that there is only one configuration naming context per forest, and that every domain controller in the forest has a writeable copy of the configuration directory partition.
Currently, the GPO code (WIP) currently makes an LDAP query to retrieve the configNC attribute from the rootDSE entry. However, since we already make an LDAP query for the rootDSE entry when an LDAP connection is made, it would be useful if the configNC attribute was also retrieved at that point, and stored somewhere from which it could be accessed by the GPO code (so that the GPO code would not need to make another LDAP query).
Fields changed
rhbz: => todo
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
priority: major => minor
milestone: SSSD 1.12 beta => SSSD 1.12.1 summary: [RFE] Enable rootDSE code to retrieve configurationNamingContext attribute => Enable rootDSE code to retrieve configurationNamingContext attribute type: enhancement => task
review: 0 => 1
milestone: SSSD 1.12.1 => SSSD 1.13 beta
mark: => 0
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
Metadata Update from @yelley: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review adjusted to on (was: 1) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3318
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.
Login to comment on this ticket.