[RFE] SID-Mapping: Store non-POSIX users in cache if they have a SID

[sssd-bot]

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

• Created at 2013-10-10 10:39:02 by sbose
• Closed at 2020-03-24 14:11:28 as wontfix
• Assigned to preichl

---

If the POSIX IDs are managed externally, e.g. by AD, not all available users and groups might have a POSIX ID assigned. But if these users or groups are IPA or AD objects and a SID we might want to store them in the cache to make SID-to-name mapping possible for these objects as well.

Currently non-POSIX groups are already saved in the cache, because we might need them to follow nested-groups hierarchies.

Non-POSIX users are currently rejected but should be handled similar as non-POSIX groups. Since I currently do see a use-case we can still reject them if they do not have a SID assigned.

Comments

---

Comment from dpal at 2013-10-10 15:44:06

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
priority: major => critical

---

Comment from dpal at 2013-11-07 15:54:41

Fields changed

rhbz: => 0

---

Comment from dpal at 2013-11-09 02:57:36

Fields changed

summary: SID-Mapping: Store non-POSIX users in cache if they have a SID => [RFE] SID-Mapping: Store non-POSIX users in cache if they have a SID
type: defect => enhancement

---

Comment from jhrozek at 2014-04-30 17:11:27

Fields changed

owner: somebody => preichl

---

Comment from preichl at 2014-05-22 11:35:53

Fields changed

patch: 0 => 1

---

Comment from jhrozek at 2014-05-30 15:43:50

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.0

---

Comment from jhrozek at 2014-07-02 12:59:20

Pavel is on vacation, we will not block the 1.12.0 release and we'll merge the patches when Pavel is back.

milestone: SSSD 1.12.0 => SSSD 1.12.1

---

Comment from jhrozek at 2014-07-02 13:02:51

Fields changed

changelog: => N/A, not directly visible to the end user.
design: => N/A not needed

---

Comment from jhrozek at 2014-09-08 20:08:43

Mass-moving all tickets that didn't make 1.12.1 into 1.12.2

milestone: SSSD 1.12.1 => SSSD 1.12.2

---

Comment from jhrozek at 2014-09-30 19:06:11

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

---

Comment from jhrozek at 2014-10-22 22:30:09

No downstream is blocked waiting for this release, lowering priority

mark: => 0
priority: critical => major

---

Comment from preichl at 2014-10-23 10:28:56

Revised patches are on the list for some time.

---

Comment from jhrozek at 2014-11-19 18:30:31

RFEs should be commited to the next release, 1.12.3 is mostly stabilizing now.

milestone: SSSD 1.12.3 => SSSD 1.12.4

---

Comment from jhrozek at 2015-01-14 11:22:32

I would prefer if the patches were only pushed to master since no downstream requires this functionality.

milestone: SSSD 1.12.4 => SSSD 1.13 alpha

---

Comment from jhrozek at 2015-02-19 14:34:38

Jan doesn't need this functionality urgently and the patches need to be rebased anyway, so let's bump the ticket to backlog.

milestone: SSSD 1.13 alpha => SSSD 1.13 backlog

---

Comment from jhrozek at 2016-02-16 15:40:29

At the moment we don't plan on implementing this in the next upstream release.

milestone: SSSD 1.13 backlog => SSSD 1.15 beta
sensitive: => 0

---

Comment from sbose at 2017-02-24 14:25:18

Metadata Update from @sbose:

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

---

Comment from thalman at 2020-03-13 13:44:42

Metadata Update from @thalman:

• Custom field design_review reset (from 0)
• Custom field mark reset (from 0)
• Custom field patch adjusted to on (was: 1)
• 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 tagged with: Canditate to close

---

Comment from pbrezina at 2020-03-24 14:11:27

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

---

Comment from pbrezina at 2020-03-24 14:11:29

Metadata Update from @pbrezina:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)