Invalid connector configuration (RelationalDatabase) when database is unavailable

[Joseph Fischetti]

> The best option is "never rely on a remote source of data that has any realistic chance of failing".

I agree completely, which is why I want to build my configuration to be available, regardless of what happens to servers that are out of my control. I can build support for this SP/attribute, without relying on the backend database for unrelated attributes.

I have no intentions of mirroring the database just for this specific SP, and I don't want users to lose access to other SSO/Federated services just because this one database has gone offline. 

Doesn't everything have a "realistic chance of failing"? However remote that may be?



Joseph Fischetti 
Linux System Administrator 
Marist College