Learn more about these different git repos.
Other Git URLs
Currently UPNs are stored in the negcache with a prefix with @ since commit https://github.com/SSSD/sssd/commit/62df78512145db94b51c5573d4df1737197e368a
@
But it would be nicer if there was a wrapper to add a UPN so that reading the code is easier to make the developer realize this is actually UPN. See https://github.com/SSSD/sssd/pull/31 for the discussion.
Since we are changing NSS to use cache_req, it would be better to do this change together with moving NSS to cache_req.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.15 Beta owner: somebody => mzidek
rhbz: => 0
Metadata Update from @jhrozek: - Issue assigned to mzidek - Issue set to the milestone: SSSD 1.15.3
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue close_status updated to: None - Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)
Metadata Update from @jstephen: - Issue assigned to jstephen (was: mzidek)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: cleanup-future, easyfix
It looks like this is already solved with:
https://pagure.io/SSSD/sssd/issue/3313
diff --git a/src/responder/common/negcache.c b/src/responder/common/negcache.c --- a/src/responder/common/negcache.c +++ b/src/responder/common/negcache.c @@ -543,0 +561,18 @@ +int sss_ncache_set_upn(struct sss_nc_ctx ctx, bool permanent, + struct sss_domain_info dom, const char *name) <snip>
Metadata Update from @jstephen: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Yes, I'm sorry this wasn't caught earlier. Nonetheless, closing.
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
@jhrozek. It was closed as a duplicate but it is not clear of which ticket.
Metadata Update from @lslebodn: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
See Justin's comment above, it's a duplicate of #3313
I missed that. Sorry for noise and thank you very much for answer. Now info about duplicate a link to ticket are close :-)
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/4237
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.