#2167 [RFE] Allow SSSD to issue shadow expiration warning even if alternate authentication method is used
Closed: Fixed None Opened 10 years ago by dpal.

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

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

SSSD checks expiration in the authentication phase while in case of login with SSH keys SSSD is called only in the accounting phase so the request is to check the account validity in the accounting phase and give expiration warnings.


Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
summary: Allow SSSD to issue shadow expiration warning even if alternate authentication method is used => [RFE] Allow SSSD to issue shadow expiration warning even if alternate authentication method is used
testsupdated: => 0
type: defect => enhancement

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

description: Ticket was cloned from Red Hat Bugzilla (product ''RHEL RFE''): [https://bugzilla.redhat.com/show_bug.cgi?id=1036745 Bug 1036745]

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

{{{
SSSD checks expiration in the authentication phase while in case of login with SSH keys SSSD is called only in the accounting phase so the request is to check the account validity in the accounting phase and give expiration warnings.
}}} => Ticket was cloned from Red Hat Bugzilla (product ''RHEL RFE''): [https://bugzilla.redhat.com/show_bug.cgi?id=1036745 Bug 1036745]

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

SSSD checks expiration in the authentication phase while in case of login with SSH keys SSSD is called only in the accounting phase so the request is to check the account validity in the accounting phase and give expiration warnings.

Fields changed

mark: => 0

Assigning to Pavel per his request.

owner: somebody => preichl

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.12.4

Bumping priority because the ticket is requested by downstream.

priority: major => critical

Fields changed

patch: 0 => 1

Moving tickets that didn't make the 1.12.4 release to 1.12.5

milestone: SSSD 1.12.4 => SSSD 1.12.5

resolution: => fixed
status: new => closed

Metadata Update from @dpal:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12.5

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

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