#3310 Support delivering non-POSIX users and groups through the IFP and PAM interfaces
Closed: Fixed Opened by jhrozek.

Many projects depend on SSSD now to support application integration through Apache modules or directly through SSSD's D-Bus interface. And often, the users and groups in the directory have no POSIX attributes. We should support these use-cases, in particular:
- look up users and groups through the D-Bus interface
- look up group membership through the D-Bus interface including membership in non-POSIX groups
- test authentication and access control through PAM


For the record, use case that triggered this ticket is an application using FreeIPA apache modules, i.e. mod_authnz_pam, mod_intercept_form_submit, mod_lookup_identity.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1425891

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1425891 1425891]

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.15.2

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.2

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch adjusted to on (was: false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

  • master:
    • 861ab44e8148208425b67c4711bc8fade10fd3ed
    • 3e39806177e1cd383743ff596cb96df44a6ce8c9
    • ed0cdfcacc44e4e13e1524e254efa744610a87c2
    • 901396366075dc3e3fcc0894345af1b51052ac69
    • 5f7f249f2a8a1c7284e991aa64dbf850d482b0aa
    • 3e789aa0bd6b7bb6e62f91458b76753498030fb5
    • 57eeec5d735c7a3bbe58299fded97414626d85f1
    • b010f24f4d96d15c5c85021bb4aa83db25cd3df5
    • 35f0f5ff9dac790f6c947190fcdc00d01ae9077c
    • cee85e8fb9534ec997e5388fce59f392cf029573
    • 825e8bf2f73a815c2eceb36ae805145fcbacf74d
    • 6324eaf1fb321c41ca9883966118df6d45259b7e

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

and related bug introduced by previous patches
https://pagure.io/SSSD/sssd/issue/3418

Metadata Update from @lslebodn:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

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/4343

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata