Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1206121

Summary: ldap_access_order=ppolicy: Explicitly mention in manpage that unsupported time specification will lead to sssd denying access
Product: Red Hat Enterprise Linux 6 Reporter: Kaushik Banerjee <kbanerje>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: grajaiya, jgalipea, jhrozek, lslebodn, mkosek, mzidek, pbrezina, preichl
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.12.4-25.el6 Doc Type: Bug Fix
Doc Text:
No documentation needed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 06:43:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kaushik Banerjee 2015-03-26 11:05:11 UTC
Description of problem:
I was not sure about how sssd should behave if an unsupported time format is used.

But it seems, sssd denies access if the time format is unsupported. Good to explicitly mention it in the manpage?

I wrote up a modified description. Does it make sense?
ppolicy: use account locking. If set, this option denies access in case that ldap attribute ´pwdAccountLockedTime´ has value of ´000001010000Z´ or represents any time in the past. The value of ´pwdAccountLockedTime´ attribute must end with ´Z´ as only UTC time zone is currently supported otherwise access is denied for any other time specifications.


Version-Release number of selected component (if applicable):
sssd-1.12.4-18.el6.x86_64

How reproducible:


Steps to Reproduce:
1. I used a time in future:
pwdAccountLockedTime= 20160830003750+0000

2.
3.

Actual results:
User access is denied and sssd cannot parse this value and prints:
[is_account_locked] (0x0400): sss_utc_to_time_t failed with 1432158251:Time specification not supported

Expected results:


Additional info:

Comment 2 Pavel Reichl 2015-03-26 16:27:05 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2612

Comment 3 Jakub Hrozek 2015-03-27 15:29:31 UTC
Fixed upstream:
    master: 1426ee8756a1df4ec0651417dce92e1dcc8a246d
    sssd-1-12: b025247b620206d31917cd5fb40943b1f2c55201

Comment 5 Kaushik Banerjee 2015-03-30 10:44:39 UTC
Verified in sssd-1.12.4-25.el6

The additional text in the manpage has:
Other time zones are not currently supported and will result in "access-denied" when users attempt to log in.

Comment 7 errata-xmlrpc 2015-07-22 06:43:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1448.html