InCommon Operations Notifications

[Nick Roy <>]

A couple meetings ago, Scott requested that we look at adding an entity
category that would be self-assertable by SPs that don't consume
metadata.  That would enable people who need to do key rollover on their
IdP to know which SPs to reach out to and work through the change
management problem with.

It occurs to me that we could do something like this:

1) Publish an IdP in metadata
2) Set its HTTP Redirect and HTTP post endpoints to values X and Y on day 1
3) Initiate with that IdP with each SP in metadata, record results
4) On day 2, update that IdP's configuration and its metadata to change
the endpoint locations
5) On day 4 (after having waited for metadata to propagate), repeat step
(3), record results
6) Compare results from (3) with (5) and label SPs that did not respond
to (3), or responded to (3) but not (5) as metadata non-refreshers

Scott, it seems like you could do at least part of this with any
existing IdP in metadata using a script.  Would that get you over the
hump with your key rollover until ops could look at automating a check
like this?

Thanks,

Nick