Learn more about these different git repos.
Other Git URLs
The first implementation of the trusts solution takes SID of the user entry and uses a special algorithm to create unique UID for the user. The similar approach is used for GID. This works fine for the deployments that do not have POSIX attributes defined in AD. In the cases when POSIX attributes are defined in AD there are usually already clients that leverage these attributes so switching to the SID->UIS/GID model is not acceptable. Instead IPA and SSSD should be able to respect the POSIX attributes defined in the AD.
IPA ticket https://fedorahosted.org/freeipa/ticket/2904
Fields changed
description: The first implementation of the trusts solution takes SID of the user entry and uses a special algorithm to create unique UID for the user. The similar approach is used for GID. This works fine for the deployments that do not have POSIX attributes defined in AD. In the cases when POSIX attributes are defined in AD there are usually already clients that leverage these attributes so switching to the SID->UIS/GID model is not acceptable. Instead IPA and SSSD should be able to respect the POSIX attributes defined in the AD. => The first implementation of the trusts solution takes SID of the user entry and uses a special algorithm to create unique UID for the user. The similar approach is used for GID. This works fine for the deployments that do not have POSIX attributes defined in AD. In the cases when POSIX attributes are defined in AD there are usually already clients that leverage these attributes so switching to the SID->UIS/GID model is not acceptable. Instead IPA and SSSD should be able to respect the POSIX attributes defined in the AD.
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => todo
proposed_priority: => Blocker
type: defect => enhancement
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: SSSD 1.11 beta => SSSD 1.10 beta
priority: major => blocker
design: => design_review: => 0 fedora_test_page: => selected: => Want
priority: blocker => critical
review: => 1
As discussed on a separate meeting Sumit will be working on this feature post-1.10 as part of providing better experience for migration to trusts solution.
Moving to 1.11 beta.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
milestone: SSSD 1.12 beta => SSSD 1.11 beta
Moving open tickets from 1.11 beta to 1.11 beta2
milestone: SSSD 1.11 beta => SSSD 1.11 beta 2
changelog: => milestone: SSSD 1.11 beta 2 => SSSD 1.11 beta 3
This is a tracker -> changing to task
type: enhancement => task
The functionality required by this tracker was already implemented in beta2
resolution: => fixed status: new => closed
summary: [RFE] It should be possible to use uid/gid defined in AD instead of SIDs => It should be possible to use uid/gid defined in AD instead of SIDs
design: => http://www.freeipa.org/page/V3/Use_posix_attributes_defined_in_AD rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1002651 1002651]
Metadata Update from @dpal: - Issue set to the milestone: SSSD 1.11.0
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/2450
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.