[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locking of principales due to unsuccessfull attempts

To: ahaupt@ifh.de
Subject: Re: Locking of principales due to unsuccessfull attempts
From: Luke Howard <lukeh@PADL.COM>
Date: Wed, 8 Jun 2005 23:12:52 +1000
Cc: feiler@uni-hohenheim.de, heimdal-discuss@sics.se, mack@uni-hohenheim.de
Organization: PADL Software Pty Ltd
References: <Pine.GSO.4.53.0506071430440.21243@maren2.rz.uni-hohenheim.de> <Pine.LNX.4.63.0506081026310.32681@fuchur.ifh.de>
Reply-To: lukeh@PADL.COM
Sender: owner-heimdal-discuss@sics.se
Versions: dmail (bsd44) 2.6d/makemail 2.10


>Well, years ago, I asked the same question. That time I was told that the 
>current database model does not support account locking (but Love and 
>Johan will probably know better...).

For our XAD identity server, which supports account locking, we added
an auditing code path to the Heimdal KDC. I mentioned it to Love some
time ago, I'm happy to commit it once approved.

-- Luke

--

Follow-Ups:
- Re: Locking of principales due to unsuccessfull attempts
  - From: Andrew Bartlett <abartlet@samba.org>

References:
- Locking of principales due to unsuccessfull attempts
  - From: Mathias Feiler <feiler@uni-hohenheim.de>
- Re: Locking of principales due to unsuccessfull attempts
  - From: Andreas Haupt <ahaupt@ifh.de>

Prev by Date: Re: Locking of principales due to unsuccessfull attempts
Next by Date: Re: TGT forwarding when cross-realm auth?
Prev by thread: Re: Locking of principales due to unsuccessfull attempts
Next by thread: Re: Locking of principales due to unsuccessfull attempts
Index(es):
- Date
- Thread