Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

store the plain user name when storing subdomain users #3048

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

store the plain user name when storing subdomain users #3048

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2006

  • Created at 2013-06-27 19:21:16 by jhrozek
  • Closed as Duplicate
  • Assigned to mzidek

Due to issues we've had with ghost users, we are storing the subdomain users with fully qualified name in the "name" attribute. But during some operations (like guessing the UPN) it would be handy to know the name instead of parsing it out of the fqdn.

Comments


Comment from dpal at 2013-07-11 15:45:03

Fields changed

milestone: NEEDS_TRIAGE => Interim Bucket
rhbz: => 0
type: defect => task


Comment from dpal at 2013-07-30 12:54:43

Fields changed

milestone: Interim Bucket => SSSD 1.12 beta


Comment from mzidek at 2014-04-03 21:17:19

Fields changed

owner: somebody => mzidek


Comment from jhrozek at 2014-05-30 16:03:38

Should be done together with the rest of the sysdb refactor Michal is working on.

milestone: SSSD 1.12 beta => SSSD 1.13 beta


Comment from dpal at 2014-09-26 18:49:57

Fields changed

mark: => 0


Comment from jhrozek at 2015-02-10 16:43:11

Duplicate of #2011

resolution: => duplicate
status: new => closed


Comment from jhrozek at 2017-02-24 15:07:10

Metadata Update from @jhrozek:

  • Issue assigned to mzidek
  • Issue set to the milestone: SSSD 1.13.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants