Question about FailOverDataConnector

[Wessel, Keith]

Nope, seems to work fine. If I include it in exportAttributes for both the primary and fail over, like I said, it resolves attributes for both. If I include it in just the primary, it behaves as expected. I suspect that it's working because the fail over logic resolves the attribute then returns it to the failed primary data connector as if it had resolved it, or at least that's how the documentation on fail overs on the wiki makes it sound.

Keith


-----Original Message-----
From: Cantor, Scott <cantor.2 at osu.edu> 
Sent: Monday, January 29, 2024 11:56 AM
To: Shib Users <users at shibboleth.net>
Cc: Wessel, Keith <kwessel at illinois.edu>
Subject: Re: Question about FailOverDataConnector

> The attribute being used by this data connector is exported directly and
> used in an attribute registry definition. I also had an exportAttributes
> parameter on the fail-over connector which was causing it to be called
> directly. I removed it, and it's now only resolving from the fail-over
> connector when the primary fails.

I don't actually know how that feature manifests. I'd have thought that you'd need it on the failover to get it exported, but I also don't know whether the exported feature is recognized when the code decides what it has to resolve.

I'm somewhat surprised that works sanely, you might want to test all that a bit. Worst case just add an AttributeDefinition in place of the export feature.

-- Scott