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

Use a different RDN attribute in sysdb #3697

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

Use a different RDN attribute in sysdb #3697

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

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

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

  • Created at 2015-05-22 17:11:54 by jhrozek
  • Closed as Invalid
  • Assigned to nobody

We should migrate away from using the object name in RDN but should use a different attribute instead. For AD users, we can consider objectSID, but as a general rule, we should not care about DN and RDN when doing sysdb searches.

Then we would be able to rename and renumber objects without having to remove and re-add them.

Comments


Comment from jhrozek at 2015-05-27 21:06:36

internal change

rhbz: => 0


Comment from jhrozek at 2015-05-28 15:42:58

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 beta


Comment from jhrozek at 2016-02-16 14:08:47

We're migrating to using FQDN as RDN, so I'm going to defer this ticket.

milestone: SSSD 1.14 beta => SSSD Deferred
sensitive: => 0


Comment from jhrozek at 2016-11-17 11:40:11

I suggest we close this ticket now that we are using FQDNs for users and groups.

review: 0 => 1


Comment from jhrozek at 2016-11-25 09:50:20

Fields changed

resolution: => wontfix
status: new => closed


Comment from jhrozek at 2017-02-24 14:46:46

Metadata Update from @jhrozek:

  • Issue set to the milestone: SSSD Patches welcome
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

1 participant