Optimizing IdP's performance

[Chad La Joie]

Ah, that's right, I forgot about the whole JAAS stateless LoginModule thing.

On Mon, Aug 1, 2011 at 13:07, Daniel Fisher <dfisher at vt.edu> wrote:
> On Mon, Aug 1, 2011 at 10:46 AM, Manuel Haim <haim at hrz.uni-marburg.de>
> wrote:
>>
>> Chad,
>>
>> thank you for your response and helpful recommendations.
>>
>> > I *strongly* discourage people from simply creating the DN from given
>> > input from the user.  It's a very brittle setup and I would remove any
>> > such suggestion added to the wiki.  If that extra search, done via
>> > pooled connections, is such a onerous amount of work then the problem
>> > is with your LDAP.
>>
>> Well, yes. However, it seems that the SearchDnResolver does not make use
>> of pooled connections yet. In our setup, this not only impaired the
>> latency, but also resulted in less logins per second (compared to using
>> a static DN). Is connection pooling planned here for a future release?
>>
>
> Early versions of the 2.x IDP attempted to use connection pooling for DN
> resolution, with mixed results due to some bugs. Ultimately we decided it
> simply violated the stateless nature of JAAS and moved to the current
> implementation which opens and closes a connection for every DN lookup. Open
> a feature request for this, it's a good time for me to review this again.
> --Daniel Fisher
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered