[RFE] Implement 3rd party ID mapper in SSSD

[sssd-bot]

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

• Created at 2012-11-12 17:15:57 by dpal
• Closed at 2020-03-24 14:20:35 as wontfix
• Assigned to yelley

---

Allow SSSD to use the same ID mapper as other 3rd party vendors.

For example this:
http://rc.quest.com/gitweb/gitweb.cgi?p=vasidmap.git

Comments

---

Comment from dpal at 2012-11-15 14:43:47

It seems that Likewise has a different custom user mapper too.

---

Comment from dpal at 2012-11-15 19:39:37

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
owner: somebody => yelley
priority: major => minor
rhbz: => todo

---

Comment from dpal at 2012-12-20 23:33:42

Fields changed

selected: => Not need

---

Comment from dpal at 2013-01-02 15:32:09

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

---

Comment from dpal at 2013-12-02 21:19:54

Fields changed

type: defect => enhancement

---

Comment from dpal at 2014-09-26 18:49:57

Fields changed

mark: => 0

---

Comment from jhrozek at 2015-02-10 17:07:00

Fields changed

changelog: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: minor => trivial
review: => 0

---

Comment from jhrozek at 2015-02-12 20:36:11

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major

---

Comment from dpal at 2017-02-24 14:22:06

Metadata Update from @dpal:

• Issue assigned to yelley
• Issue set to the milestone: SSSD Patches welcome

---

Comment from pbrezina at 2020-03-24 14:20:34

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:20:36

Metadata Update from @pbrezina:

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