#2374 audit used sssd backend
Closed: Invalid None Opened 9 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1115189

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:

sssd allows different backends to be used for obtaining user credentials. This
includes the ability to use multiple backends or transparently switch to
another backend.

For better auditing, sssd or its PAM/NSS module should audit the origin of the
credential credentials used to log a user in.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.12.1
review: True => 0
selected: =>
testsupdated: => 0

After some discussion, we decided to implement this in PAM completely, without SSSD involvement.

resolution: => wontfix
status: new => closed

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

7 years ago

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

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.

Login to comment on this ticket.

Metadata