[External] Re: Activation Conditions and AbstractAttributePredicate warning after IDPv4 Upgrade
michael-domingues at uiowa.edu
Tue Dec 8 22:14:39 UTC 2020
For what it's worth, this is during IDP startup (prior to any authentication events) on an IDPv4 deployment installed directly over a working IDPv3 system. No configuration changes are involved save those necessary to resolve deprecation warnings.
I'm happy to file a bug report on this, but it's clearly happening, it's repeatable, and the warnings aren't present in IDPv3.
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Tuesday, December 8, 2020 3:16 PM
To: Shib Users <users at shibboleth.net>
Subject: [External] Re: Activation Conditions and AbstractAttributePredicate warning after IDPv4 Upgrade
On 12/8/20, 3:43 PM, "users on behalf of Domingues, Em" <users-bounces at shibboleth.net on behalf of michael-domingues at uiowa.edu> wrote:
> I've read through the docs and poked around the relevant IDP source but am currently at a loss trying to explain why
> this would happen. Is there something I'm missing here?
It's not possible, so something crucial is being left out, and I'd probably need a bug with a full DEBUG log to guess what's missing. Maybe proxying is involved, but something has to be causing the context to be empty in one case and not another.
The point at which the condition is evaluated and the state of the tree is the same as V3, only the underlying object that contains the condition is different.
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users