Learn more about these different git repos.
Other Git URLs
Currently the range-type ipa-ad-trust-posix will read the UID and the GID of the primary group of the user from AD. If user private groups should be used for trusted users an unique group with matching GID must be created in AD for each user.
To simplify this a new range-type like e.g. ipa-ad-trust-posix-upg can be added which will instruct SSSD to generate a user private group on the fly and move the group related to the original GID to the secondary group, as it is done for algorithmic mapping already.
If this should be implemented a matching SSSD has to be created because the main work is done by SSSD here.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1327705 (Red Hat Enterprise Linux 7)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1327705 1327705]
Fields changed
milestone: NEEDS_TRIAGE => SSSD Future releases (no date set yet)
Metadata Update from @sbose: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue set to the milestone: SSSD 1.16.0 (was: SSSD Future releases (no date set yet))
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: RFE
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: postpone-to-future-releases
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue untagged with: postpone-to-future-releases - Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.16.1)
Metadata Update from @thalman: - Custom field design_review adjusted to on (was: false) - Custom field mark adjusted to on (was: false) - Custom field patch adjusted to on (was: false) - Custom field review adjusted to on (was: false) - Custom field sensitive adjusted to on (was: false) - Custom field testsupdated adjusted to on (was: false) - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
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/4280
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.