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 brent.atkinson@gmail.com
 designates 209.85.210.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPCVKoKJ4-Q1HhwPWUKPPS0UvNRdwkYd0yZudvFKdacPCR__mA@mail.gmail.com>
References: 
 <CAPbd=T7LLq-nAiMwreMC_9WON_D=H9nCJvs01_KwLguF_n-KzQ@mail.gmail.com>
	<CAPCVKoKJ4-Q1HhwPWUKPPS0UvNRdwkYd0yZudvFKdacPCR__mA@mail.gmail.com>
Date: Wed, 24 Aug 2011 13:44:44 -0400
Message-ID: 
 <CALyHw0H43SZZuqOMLGyRKkKY-jWb-r1bHVpM9MN0zAkYcB2-JA@mail.gmail.com>
Subject: Re: Archiva issue with LDAP (MRM-1488)
From: Brent Atkinson <brent.atkinson@gmail.com>
To: dev@archiva.apache.org
Content-Type: multipart/alternative; boundary=bcaec5299fc119dd9004ab43de3b

--bcaec5299fc119dd9004ab43de3b
Content-Type: text/plain; charset=ISO-8859-1

Hi everyone,

I actually ran into this when fixing the connection leaks. I realized it was
probably building in too many assumptions, but I created and held onto the
LdapCtxFactory in redback's LdapConnection for a very specific reason:
connection pooling. The sun JNDI ldap implementation can pool connections
sharing the same credentials *and config options* as long as they are
created from the same LdapCtxFactory.

http://download.oracle.com/javase/jndi/tutorial/ldap/connect/pool.html

Brent

On Wed, Aug 24, 2011 at 8:57 AM, Wendy Smoak <wsmoak@gmail.com> wrote:

> 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
>

--bcaec5299fc119dd9004ab43de3b--