You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2656
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:
The text was updated successfully, but these errors were encountered: