Generally cached data should live as long as possible. However, because the metadata has a 48-hour "validUntil" attribute, we would need to clear the cache at least that often, otherwise our login breaks.
There are a few solutions:
For our purpose, being able to disable the validUntil attribute entirely would be the best, then there are no synchronization issues at all.
At the very least, if there was some way to force the metadata to regenerate once the 48-hour mark was reached, that would be good.
Thanks in advance.
Fixed
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
For our purpose, being able to disable the validUntil attribute entirely would be the best, then there are no synchronization issues at all.
Note that as of May 2024, per https://github.com/SAML-Toolkits/php-saml/pull/569 , php-saml now includes a parameter to exclude validUntil.