Handling empty LDAP connection pools on IdP start-up

[Wessel, Keith]

Adding the validatorRef to my data connector did the trick. Now, if the whole LDAP cluster is down on restart, the pool at least continues to try and make connections and the attribute resolver starts working once a connection is successfully added to the pool. That's what I wanted.

Scott, adding the fallback static connector would allow my other data connectors to continue functioning even if one was down and would also prevent run-time errors, correct? What would this static connector look like? That is what attributes, if any, would be in it?

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, March 09, 2017 11:19 PM
To: Shib Users <users at shibboleth.net>
Subject: RE: Handling empty LDAP connection pools on IdP start-up

> Ah, the resolver component validation.
> add validatorRef="shibboleth.NonFailFastValidator" to your LDAPDirectory
> element.

Yep, forgot I have that too.

But I still suggest failing over to a static connector, otherwise you're going to get failures at runtime if the directory is unavailable, which I assume is possible or it wouldn't be down when you restarted either.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net