Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (nike.apache.org: domain of cmcamerino@gmail.com designates
 209.85.132.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=WkBuwyA3GrVkVvR4QycdY57zJAcVMkO3UmqfYD3lhyFjVL/SI44JnM9gbKqHcPJfU6
         ni8DMKqJBLiuiIvR0HBJHIX81VXj00Bh43nWR5B9sPzcjYMUJoku3gU8rcE5QtbIqEvC
         h3idbzZyK1vpMhYhOISwZ3KDQ1TswVnVOYwmY=
MIME-Version: 1.0
In-Reply-To: <49FCB3C3.3060807@labeo.de>
References: <37cc2c090905020944k3150e9caibec8178543bc06bf@mail.gmail.com>
	 <49FCB3C3.3060807@labeo.de>
Date: Sun, 3 May 2009 07:17:19 +0800
Message-ID: <37cc2c090905021617g9df8334mc9debb0f7747e72a@mail.gmail.com>
Subject: Re: Force Change Password
From: Carlo Camerino <cmcamerino@gmail.com>
To: users@directory.apache.org
Content-Type: multipart/alternative; boundary=0016e64616e67d8b550468f6212b

--0016e64616e67d8b550468f6212b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

Thank you for reply :)

I will continue with my evaluation.

Thanks
Carlo

On Sun, May 3, 2009 at 4:57 AM, Stefan Zoerner <stefan@labeo.de> wrote:

> Hi Carlo,
>
> Carlo Camerino wrote:
>
>> I just want to know if Apache Directory server can do the following.
>>
>> 1.) Can it force the users to change password? (Expire password after a
>> specific time period)
>> 2.) Can I make a list of commonly used passwords that users shouldn't use?
>>
>
> The functionality w.r.t. password polices is not that impressive yet. There
> is a Password Policy Interceptor, which has to be enabled. It deals with
> minimal password complexity etc. defaults (if enabled) to this:
>
> * The password is at least six characters long.
> * The password contains a mix of characters.
> * The password does not contain three letter (or more) tokens from the
> user's account name.
>
> It would be quite easy to extend it to forbid certain password values. But
> you have to extend the corresponding class and modify the configuration in
> server.xml to accomplish that.
>
> This helps at least for question 2 (hopefully).
>
> Greetings from Hamburg,
>    Stefan
>
>
>
>

--0016e64616e67d8b550468f6212b--