Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 718062 - When admin resets a user's password with "ipa passwd" user's failed log in count is not reset
When admin resets a user's password with "ipa passwd" user's failed log in co...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa (Show other bugs)
6.1
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Rob Crittenden
Chandrasekar Kannan
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-30 16:41 EDT by Jenny Galipeau
Modified: 2015-01-04 18:49 EST (History)
4 users (show)

See Also:
Fixed In Version: ipa-2.1.0-1.el6
Doc Type: Bug Fix
Doc Text:
Do not document
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-06 13:41:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1533 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-05 20:23:31 EST

  None (edit)
Description Jenny Galipeau 2011-06-30 16:41:31 EDT
Description of problem:

Once a user has reached max failed login attempts, an admin should be able to reset the password with ipa passwd and this should reset the failed login counter back to 0.  It is not resetting the counter

Version-Release number of selected component (if applicable):
ipa-server-2.0.99-2.20110629T0200zgit66eeace.el6.x86_64

How reproducible:


Steps to Reproduce:
1. add a new user and set the user's password
2. kinit as the user and change the password
3. kinit as the user with an invalid password
4. kinit as admin and check the user's failure count.
   # ipa user-show --all <userid>

   should see "krbloginfailedcount: 1"
5. reset the user's password as an admin
   # ipa passwd <userid>
6. check the user's failure count.
   # ipa user-show --all <userid>

   should see "krbloginfailedcount: 0"
  
Actual results:
Counter is not reset when password is reset by an admin

Expected results:
Counter to be reset to 0, when password is reset by an admin

Additional info:
Comment 2 Rob Crittenden 2011-07-06 11:36:16 EDT
https://fedorahosted.org/freeipa/ticket/1441
Comment 4 Jenny Galipeau 2011-07-14 09:00:16 EDT
Verified:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Verify Failure Counter Reset with Admin Password Reset
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: ERROR: kinit as user1 with password BADPWD failed.
:: [   PASS   ] :: Kinit as user with invalid password
:: [   LOG    ] :: kinit as admin with password Secret123 was successful.
:: [   PASS   ] :: Running 'kinitAs admin Secret123'
:: [   PASS   ] :: User's failed counter is as expected: [1]
:: [   LOG    ] :: kinit as admin with password Secret123 was successful.
:: [   PASS   ] :: Running 'kinitAs admin Secret123'
:: [   PASS   ] :: Verify Password Change was successful.
:: [   PASS   ] :: User's failed counter is as expected: [0]
:: [   LOG    ] :: Duration: 16s
:: [   LOG    ] :: Assertions: 6 good, 0 bad
:: [   PASS   ] :: RESULT: Verify Failure Counter Reset with Admin Password Reset

version:
ipa-server.x86_64 0:2.0.99-3.20110713T1714zgit02520ab.el6


Waiting for all acks and for bug to be in modified state before marking bug verified.
Comment 7 Rob Crittenden 2011-10-31 16:44:39 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document
Comment 8 Gowrishankar Rajaiyan 2011-11-02 14:32:42 EDT
Marking as VERIFIED as per comment #4.
Comment 9 errata-xmlrpc 2011-12-06 13:41:01 EST
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.

http://rhn.redhat.com/errata/RHSA-2011-1533.html

Note You need to log in before you can comment on or make changes to this bug.