Error with SPs registered with InCommon
Cantor, Scott
cantor.2 at osu.edu
Tue Feb 18 17:13:24 UTC 2025
> That means those IDPs have been unable to load/refresh
> InCommon metadata for two weeks already, i.e., they're
> were essentially broken already.
No, they didn't fail until InCommon floated the validUntil out past the historical 2 week interval it's been set to, tripping the filter to start rejecting it.
The most I would say is warnings should be paid attention to, particularly in critical categories like metadata classes. Logs do nobody any good if people don't read them or alert on them.
> The question those folks should be asking themselfs is why
> their IDP stopped updating InCommon metadata two weeks
> ago.
It hadn't, it was a recent update that broke them. It hadn't expired, it was just being treated as invalid.
Any messages about expiration have to do with the fact that it was holding on to older copies when it couldn't refresh the feed, and those copies finally expired, leaving nothing to use.
-- Scott
More information about the users
mailing list