forced refresh of SP metadata when using mdq

[Alan Buxey]

hi,

This is the same issue for the old aggregate - any urgent change, if it
could get published ASAP would still need the SP to restart the service
otherwise you'd have to wait until the local cache time expired for the SP
to go fetch the latest aggregate.   In terms of making the SP a little more
dynamic, the configuration parameters are already there in the config you
posted - maxCacheDuration and minCacheDuration - those will determine how
long the SP will keep a value for before attempting to fetch a new copy of
the entities metadata via MDQ.  I'd say that 1 minute is a little 'too
keen' for general deployment.

alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250224/1c682c32/attachment.htm>