#2656 Use a different RDN attribute in sysdb
Closed: Invalid None Opened 8 years ago by jhrozek.

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.


internal change

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

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

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

review: 0 => 1

Fields changed

resolution: => wontfix
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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/3697

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata