Bug 542687

Summary: krb5 1.7 locks AD accounts
Product: [Fedora] Fedora Reporter: arif
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 12CC: nalin, troels
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.7.1-1.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-21 10:47:47 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description arif 2009-11-30 10:05:12 EST
Description of problem:

krb5 1.7, as installed on f12, when used with an Microsoft AD server tries incorrect passwords multiple times. As AD account lockouts are often configure theis will lock a users account on the first incorrect password.


Version-Release number of selected component (if applicable):

1.6 is fine, 1.7 is broken. 


How reproducible:

100%


Steps to Reproduce:
1. configure krb5.conf to use a AD server 
2. kinit <user>
3. Enter incorrect password
  
Actual results:

$ kinit user
Password for user@example.com: 
kinit: Clients credentials have been revoked while getting initial credentials

Now the account is locked.

Expected results:

$ kinit
Password for user@example.com: 
kinit(v5): Preauthentication failed while getting initial credentials


Additional info:

See this thread on the krb5 mailing list
  http://mailman.mit.edu/pipermail/kerberos/2009-October/015368.html

See http://mailman.mit.edu/pipermail/kerberos/2009-October/015375.html for a possible patch.
Comment 1 Troels Arvin 2010-02-03 05:35:04 EST
Probably a dupe of Bug #554351.
Comment 2 Nalin Dahyabhai 2010-02-03 12:07:18 EST
(In reply to comment #1)
> Probably a dupe of Bug #554351.    

Yep, it's the same one alright.  It should be fixed in 1.7.1, which I hope to get into updates-testing today.
Comment 3 Troels Arvin 2010-09-21 04:08:05 EDT
I think this bug can be closed; I haven't seen the problem since upgrading to the fixed krb package.
Comment 4 Nalin Dahyabhai 2010-09-21 10:47:47 EDT
Alright, then.  Thanks!