Proxy IdP + activationConditions
makst at upenn.edu
Tue Jan 19 16:54:06 UTC 2021
preRequested="true" was all I needed!
I removed the activationConditionRef on my epe-proxy attribute that was used for the activationCondition since you're right, the logic doesn’t make sense.
On 1/19/21, 11:26, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
You can't have an activation condition that depends on a value of an attribute that you're actually applying the activation condition to, that would be circular.
Aside from that, any activation condition in the resolver can only depend on "prerequested attributes", with the special workrounds documented under that topic . It doesn't have access to attributes that are in the middle of being resolved. But it would be impossible for a loop like that to work either way.
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users