Adding a post authentication flow to an SP using metadata-driven configuration
kwessel at illinois.edu
Tue Oct 12 12:23:29 UTC 2021
Thanks, Scott. I think that makes sense though I would have expected the order to be reversed so I could, as I said, set defaults then override them with metadata. In this case, though, it's no problem for me to set all that I need to set with metadata.
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, October 12, 2021 7:17 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Adding a post authentication flow to an SP using metadata-driven configuration
On 10/11/21, 9:31 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:
> Is this intentional? Or should I be able to set a default and
> override it with metadata-driven settings? I can always set my default using metadata-driven settings, too, if need be.
It's intentional. There's a layering of beans, and setting the property explicitly replaces the metadata-based lookup function with a "constant" lookup function that returns the values you set. The reason being that it lets you do exactly that: use metadata for lots of stuff but then override things you want to set explicitly inline. The fact that there's a predictable order to it is intentional and a feature.
For Consortium Member technical support, see https://urldefense.com/v3/__https://shibboleth.atlassian.net/wiki/x/ZYEpPw__;!!DZ3fjg!uSHb3ONUIgsBryAS8BiE9nQY-v29LIV_P0nNspjMNJit7zRvxAJMFXgB-3JDnRBRJQ$
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users