[RFE] Allow user private groups for trusted users when POSIX attributes are coming from AD

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3247

• Created at 2016-11-24 17:24:35 by sbose
• Closed at 2020-03-13 11:27:26 as Fixed
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1327705

---

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.

Comments

---

Comment from jhrozek at 2016-12-08 17:18:41

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]

---

Comment from jhrozek at 2016-12-08 17:20:02

Fields changed

milestone: NEEDS_TRIAGE => SSSD Future releases (no date set yet)

---

Comment from sbose at 2017-02-24 14:31:22

Metadata Update from @sbose:

• Issue set to the milestone: SSSD Future releases (no date set yet)

---

Comment from jhrozek at 2017-08-10 13:48:12

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))

---

Comment from jhrozek at 2017-08-18 18:25:43

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

---

Comment from jhrozek at 2017-10-19 20:22:19

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

---

Comment from jhrozek at 2017-10-19 20:22:23

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)

---

Comment from jhrozek at 2017-12-15 19:59:51

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

---

Comment from jhrozek at 2018-01-08 20:59:37

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)

---

Comment from thalman at 2020-03-13 11:27:27

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)