Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
Received-SPF: pass (athena.apache.org: domain of wsmoak@gmail.com designates
 209.85.214.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPbd=T7LLq-nAiMwreMC_9WON_D=H9nCJvs01_KwLguF_n-KzQ@mail.gmail.com>
References: 
 <CAPbd=T7LLq-nAiMwreMC_9WON_D=H9nCJvs01_KwLguF_n-KzQ@mail.gmail.com>
From: Wendy Smoak <wsmoak@gmail.com>
Date: Wed, 24 Aug 2011 08:57:21 -0400
Message-ID: 
 <CAPCVKoKJ4-Q1HhwPWUKPPS0UvNRdwkYd0yZudvFKdacPCR__mA@mail.gmail.com>
Subject: Re: Archiva issue with LDAP (MRM-1488)
To: dev@archiva.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 24, 2011 at 2:45 AM, Deng Ching <oching@apache.org> wrote:

> We're planning to use EhCache for this so we can also set a TTL
> (time-to-live) for the cached objects. A password change done from the
> webapp would flush the user in the cache.

If you're using LDAP, would users be doing password changes from the webapp?

Making that TTL configurable by the admin would be good, then they can
trade off between extra calls to LDAP and 'how come my new password
doesn't work?'.

-- 
Wendy