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

[Wessel, Keith]

A good point, Sir. If my database is down, I'd rather have no eptid returned than a changed one. Otherwise, it defeats the purpose of a stored id connector and the benefits of persistence.

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?

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 9:42 AM
To: users at shibboleth.net
Subject: Re: StoredID data connector: what happens when the database goes down?

* Peter Schober <peter.schober at univie.ac.at> [2014-06-12 16:28]:
> * Wessel, Keith <kwessel at illinois.edu> [2014-06-12 16:17]:
> > I'm assuming that if it can't find an existing stored id for any
> > reason, whether it's that the user doesn't have one yet or the
> > database is unavailable, it just computes one. Is that correct?

If the database is availabe, it computes one and stores it.

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

Also, trying to fall back to computedId if the database becomes
unavailable isn't reasonable, as the existing (stored, persisted)
value might be different from the freshly computed one, potentially
sending a different identifier to the service (which would result in
the subject being a different one to the service, etc.)
-peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net