activationConditionRef not working?

[Mohamed Lrhazi]

It seems that  moving activationConditionRef to the DataConnector instead
of AttributeDefinition solved my problem.

Thanks! Regards

On Fri, Nov 8, 2024 at 7:45 AM Mohamed Lrhazi <lrhazi at cua.edu> wrote:

> It seems to resolve the attribute and then log this:
>
> AbstractResolverPlugin:175] - Resolver plugin 'isPatron': activation criteria not met, nothing to do
>
> pl.AttributeResolverImpl:334] - Attribute Resolver 'ShibbolethAttributeResolver': Attribute definition 'isPatron' produced no attribute
>
>
>
> Is there a way to prevent the resolution of the attribute ?
>
> Thanks,
> Mohamed.
>
>
> On Fri, Nov 8, 2024 at 7:31 AM Mohamed Lrhazi <lrhazi at cua.edu> wrote:
>
>> Hello,
>>
>> I have an attribute defined as follows:
>>
>> <AttributeDefinition id="isPatron" xsi:type="ScriptedAttribute"
>> activationConditionRef="NeedsSQLAttribs_2_Condition">
>> <InputDataConnector ref="oracledbcf_csprd_wrlc" attributeNames=
>> "cx_patron_type" />
>> <InputDataConnector ref="adLdapConnector" allAttributes="true" />
>> <Script>
>> ...
>>
>> I noticed that it is being evaluated for an SP that is not listed in
>> NeedsSQLAttribs_2_Condition
>>
>> The logs I see this:
>>
>> Attribute Resolver 'ShibbolethAttributeResolver': Resolving dependencies
>> for 'isPatron'
>>
>> I want the attribute to only be resolved for some SPs.... What am I
>> missing to get it to work that way?
>>
>> Thanks a lot,
>> Mohamed.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20241108/946de04a/attachment.htm>