All queries getting executed
Mathew, Sunil
smathew at hbs.edu
Thu Dec 8 23:57:30 UTC 2022
Thanks Scott. I saw documentation for activationCondition in services.xml, for example,
<!-- Canvas -->
<bean id="CanvasCondition" parent="shibboleth.Conditions.OR">
<constructor-arg>
<list>
<bean parent="shibboleth.Conditions.RelyingPartyId" c:candidate="http://hbs-dev.instructure.com/saml2" />
<bean parent="shibboleth.Conditions.RelyingPartyId" c:candidate="http://hbs-int.instructure.com/saml2" />
<bean parent="shibboleth.Conditions.RelyingPartyId" c:candidate="http://hbs.instructure.com/saml2" />
</list>
</constructor-arg>
</bean>
Can you please let me know how to use activation condition to limit queries from getting executed in relying-party.xml?
Sunil
From: Cantor, Scott <cantor.2 at osu.edu>
Date: Thursday, December 8, 2022 at 6:29 PM
To: Shib Users <users at shibboleth.net>
Cc: Mathew, Sunil <smathew at hbs.edu>
Subject: Re: All queries getting executed
>, We have an issue where all queries defined in attribute-resolver. xml is
> getting executed even though they are not defined in attribute-filter. xml for
> that endpoint
You have a misunderstanding. Filtering does not prevent anything, it's after the fact. Resolution always resolves everything, it's up to the activation conditions there attached to various things to actually limit something running.
-- Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20221208/ce7836b6/attachment.htm>
More information about the users
mailing list