Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 75648 invoked from network); 2 Nov 2010 15:20:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 15:20:21 -0000 Received: (qmail 78042 invoked by uid 500); 2 Nov 2010 15:20:52 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 77998 invoked by uid 500); 2 Nov 2010 15:20:50 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 77885 invoked by uid 99); 2 Nov 2010 15:20:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 15:20:50 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.160.178 as permitted sender) Received: from [209.85.160.178] (HELO mail-gy0-f178.google.com) (209.85.160.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 15:20:42 +0000 Received: by gyb13 with SMTP id 13so5321923gyb.37 for ; Tue, 02 Nov 2010 08:20:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=TqEnMPyTKwb6361/juWXsalqTreSSQOei5joL3FHAOY=; b=Jng5fkeiCiaemuYaa8D0Tma6J9NcPoRKUl4Cs8M2XvomwmSKZE/tn4Fsng3KlzZ0SN 7ePdM7ByAa2OUX9xPNrcTdqAcLdkIZK0WIwp/O3uR6Rpg9B8tUgjzPzKEOT4rOS5zkdP EOmo/42B5wkv2uKJTVPD/Aanp+aUGvxFxDaR8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=gTfrawa+jKNvrKp8EEAC5sdZPKACfJg8YnwGnkmYzFgzQJJvAU5OT4UV3z0B2rVYvy QQwyZOboMVLe3C5e9k/7d2SokV7neunEvsqWJXQcUEY3KoSHvOzpbRYl5tvqGPbbOrHS aUUXnu+3MtTvl4bq3Wa/yZaeM72XrOr6fF6L4= MIME-Version: 1.0 Received: by 10.42.148.9 with SMTP id p9mr422938icv.440.1288711220331; Tue, 02 Nov 2010 08:20:20 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.231.16.69 with HTTP; Tue, 2 Nov 2010 08:20:20 -0700 (PDT) In-Reply-To: References: Date: Tue, 2 Nov 2010 20:50:20 +0530 X-Google-Sender-Auth: cy_xOP5Gsx32xRpgshacBqT7xCY Message-ID: Subject: Re: Locking User Account in ApacheDS From: Kiran Ayyagari To: users@directory.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 11/2/10, Robert Greathouse wrote: > Hi, > > I hope this is the right list to ask this question. I am wondering if > ApacheDS has a mechanism to lock a user account? If so, how is locking > accomplished? Is it a configuration (ie: 3 failed attempts automatically > locks)? Is it a particular attribute that needs to be set programmatically? > > Thanks, > Robert G. Greathouse > Nope, it is not possible in versions upto 1.5.7. We have included password policy in the trunk (which will be released as version 2.0) using which you can achieve account locking. -- Kiran Ayyagari