StoredID data connector: what happens when the database goes down?

[Wessel, Keith]

Sorry, sure enough, you were clearer on that. I didn't read carefully enough.

Problem is the storedid dataconnector doesn't seem to include support for the failover dataconnector element. I can, if not using a container-based database configuration, define a pool of Oracle database servers, but that only helps if my database architecture is set up as such.

So, is something missing from the docs here? Or is there no alternative if the database is unavailable and, as you said, no attributes will be returned to the SP?

Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Peter Schober
Sent: Thursday, June 12, 2014 11:26 AM
To: users at shibboleth.net
Subject: Re: StoredID data connector: what happens when the database goes down?

* Wessel, Keith <kwessel at illinois.edu> [2014-06-12 16:52]:
> So, if I understand correctly, if the database is unavailable,
> attributes using the stored id connector will return nothing, but
> everything else will proceed normally. Is that correct?

No, I thought was rather specific about this:

> If a data connector becomes unavailable (and you don't have a
> failover data connector configured) the attribute resolution fails
> wholesale, IIRC.

So not just the persistentId will be missing, no attribute statement
will be generated at all (others will hopefully correct me if this is
not in fact the case). Unless, as I said, you add a failover data
connector which in this case would return nothing, successfully, for
the persistentId, leading to only the missing persistentId (which
would be bad enough, I'd imagine, for all services keying off that
data).
-peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net