AttributeResolverService not reloading on demand

Baron Fujimoto baron at hawaii.edu
Fri May 13 20:40:29 UTC 2022


We're running IdP 4.2.1. For some reason,
reloading AttributeResolverService on demand doesn't seem to be working. We
have the following in services.xml:

    <util:list id ="shibboleth.AttributeResolverResources">
        <value>%{idp.home}/conf/attribute-resolver.xml</value>
        <!-- Custom activation conditions -->
        <value>%{idp.home}/conf/activation-condition.xml</value>
    </util:list>

But if I update an attribute definition in attribute-resolver.xml (say
something simple, like changing a friendlyName), then try to reload the
AttributeResolverService with

curl -k 'https://
${idp_host}/idp/profile/admin/reload-service?id=shibboleth.AttributeResolverService'

I get the output, "Configuration reloaded for
'shibboleth.AttributeResolverService'" but it It has no effect and I don't
see the change if I do a resolvertest for the updated attribute.

However, the update to attribute-resolver.xml does appear to take effect on
the quarter hour, which seems to be consistent with
"idp.service.attribute.resolver.checkInterval = PT15M" in
services.properties

FWIW, AttributeFilterResources appears to work as expected when reloaded on
demand.

Any suggestions as to what's wrong here, or how to further troubleshoot
this?
-- 
Baron Fujimoto <baron at hawaii.edu> ::: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum descendus pantorum
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220513/4a6752e8/attachment.htm>


More information about the users mailing list