Handling empty LDAP connection pools on IdP start-up

[Wessel, Keith]

FYI, turns out empty static data connectors are valid. I created one with no attributes, added it as failover to my LDAP data connectors, and life is good.

Thanks again,
Keith


-----Original Message-----
From: Wessel, Keith 
Sent: Friday, March 10, 2017 11:09 AM
To: 'Shib Users' <users at shibboleth.net>
Subject: RE: Handling empty LDAP connection pools on IdP start-up

Thanks, Scott.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, March 10, 2017 11:01 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Handling empty LDAP connection pools on IdP start-up

On 3/10/17, 11:56 AM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

> Got it. Yeah, I don't get runtime errors with an empty pool, but I do get no attributes back even though my other data
> connectors are still functioning. Too bad there's not a way to configure failfast for a dataconnector to tell it to go ahead and
> resolve attributes from other data connectors without creating the static data connector.

I would guess that 4.0 is the right time to sit down and rethink all the failure behavior, as I've never particularly agreed with a lot of it. But there are different points of view about it.

> But your solution's easy enough. Is it valid to have a static data connector with no attributes in it, or is at least one attribute
> with one value required? 

I never tried, I think you have to have something there. I just use something I never reference anywhere.

-- Scott


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