Errors after Relying Party Service Reload

[Cantor, Scott]

> We are well aware of the warning on the wiki regarding use of the
> configuration reloading in production, and we have sufficient configuration
> testing in place to prevent invalid configurations from being loaded into the
> production environment. The goal of using the reloading features is to
> provide shorter turn-around when adding new SPs to the IdP and modifying
> attributes and release policies without resetting session state for all
> authenticated users by restarting Tomcat entirely.

None of those things requires reloading relying-party.xml.

> Given this issue, however,
> we've delayed implementation of this feature and instead scheduled a
> restart of Tomcat nightly to pick up any changes made the previous day,
> which means even the smallest change doesn't take effect until the
> following day.

There are no small changes that involve that file.

I have no idea if there's a bug or not, I don't do that kind of reloading. Just saying it isn't needed to address your requirements in general. My guess is the cache of resolved keys from metadata is corrupted somehow.

-- Scott