Learn more about these different git repos.
Other Git URLs
Now when we set trust we do the ID mapping however if the customer used centrally stored posix attributes in AD in the past he would have to do a UID/GID remapping which is really painful.
There should be an option to do an additional SID to UID lookup and get data from AD instead of using dynamic mapping.
The ticket is somewhat related to https://fedorahosted.org/sssd/ticket/1568
This came up from the first account that considers moving to the trust based solution.
milestone: NEEDS_TRIAGE => SSSD 1.11 beta
type: defect => enhancement
rhbz: => todo
milestone: SSSD 1.12 beta => SSSD 1.11 beta
review: => 0
Moving open tickets from 1.11 beta to 1.11 beta2
milestone: SSSD 1.11 beta => SSSD 1.11 beta 2
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] Allow using UIDs and GIDs from AD in trust case => Allow using UIDs and GIDs from AD in trust case
rhbz: todo => 0
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:
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.
to comment on this ticket.