You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering the dependancies needed for SSSD to function, it would be nice to have a PAM module which supported the FreeIPA HBAC without requiring dependancies for the FULL SSSD which are not available in all/older OSes.
The SSSD should provide HBAC validation as a shared library that ca be reused by IPA for the HBAC validation and emulation. This ticket will track the SSSD part of the effort covered in the IPA ticket.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/792
Considering the dependancies needed for SSSD to function, it would be nice to have a PAM module which supported the FreeIPA HBAC without requiring dependancies for the FULL SSSD which are not available in all/older OSes.
Comments
Comment from sgallagh at 2011-02-09 17:38:19
Moved to https://fedorahosted.org/freeipa/ticket/938
resolution: => invalid
status: new => closed
Comment from dpal at 2011-03-07 21:22:00
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.7.0
resolution: invalid =>
status: closed => reopened
Comment from dpal at 2011-03-07 21:23:34
The SSSD should provide HBAC validation as a shared library that ca be reused by IPA for the HBAC validation and emulation. This ticket will track the SSSD part of the effort covered in the IPA ticket.
Comment from dpal at 2011-07-22 22:13:16
As the HBAC work nears completion this ticket should be used to trac the original enhancement that JR logged. Moving it to deferred though.
milestone: SSSD 1.8.0 => SSSD Deferred
patch: => 0
Comment from dpal at 2012-01-19 03:20:48
Fields changed
rhbz: => 0
Comment from jhrozek at 2016-11-17 12:04:54
pam_hbac was already implemented.
blockedby: =>
blocking: =>
changelog: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
resolution: => fixed
review: => 0
selected: =>
sensitive: => 0
status: reopened => closed
Comment from jraquino at 2017-02-24 14:58:29
Metadata Update from @jraquino:
The text was updated successfully, but these errors were encountered: