Learn more about these different git repos.
Other Git URLs
It would be useful if we culd expose SID->Name resolution as a special case through the getpwnam()/getpwgroup() interfaces, by simply passing in a SID a string.
This will allow a number of components to do SID->Name resolution cheaply using a well-known existing interface and keep the cache in a single place within SSSD. The FreeIPA server could also benefit from this approach and defer to SSSD for SID->Name resolution.
I do not see a simple way to do Name->SID resolution through nsswitch interfaces, but that operation is less common and we can deal with it separately if needed.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10 beta rhbz: => 0 summary: Use the getpwnam()/getgrnam() interface as a gateway to resolve SID to Names => [RFE] Use the getpwnam()/getgrnam() interface as a gateway to resolve SID to Names
priority: major => critical
owner: somebody => simo status: new => assigned
design: => design_review: => 0 fedora_test_page: => selected: => Want
owner: simo => sbose status: assigned => new
review: => 0
The first batch of patches landed in master:
The patches that implement the library itself and its plugin interface were pushed to master:
resolution: => fixed status: new => closed
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=887035 887035]
changelog: => IPA Web UI is able to display real names not only SIDs. design: => N/A ((not visible to end user at the moment)
design: N/A ((not visible to end user at the moment) => N/A (not visible to end user at the moment)
design: N/A (not visible to end user at the moment) => https://fedorahosted.org/sssd/wiki/DesignDocs/NSSResponderIDMappingCalls
Metadata Update from @simo: - Issue assigned to sbose - Issue set to the milestone: SSSD 1.10 beta
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/2601
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.