#1956 Investigate and provide an alternative to enabling enumeration for pam_lastlog to work
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by dpal.

Ticket was cloned from Red Hat Bugzilla (product RHEL RFE): Bug 952188

There is an RFE that suggest to document that for the pam_lastlog to work the enumeration should be turned on. This seems like a wrong approach. pam_lastlog should work regardless of the enumeration being set.


Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.11
review: True => 0
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=952188 952188] => [https://bugzilla.redhat.com/show_bug.cgi?id=952188 952188] todo
selected: =>
summary: [RFE] Investigate and provide an alternative to enabling enumeration for pam_lastlog to work => Investigate and provide an alternative to enabling enumeration for pam_lastlog to work
testsupdated: => 0
type: enhancement => task

Start working on this at the beginning of 1.12 release.

milestone: SSSD 1.11 => SSSD 1.12 beta
priority: major => blocker

Fields changed

priority: blocker => major

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12.1

Fields changed

milestone: SSSD 1.12.1 => SSSD 1.13 beta

Fields changed

mark: => 0

Just close.

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

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

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

Metadata Update from @dpal:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/2998

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