This is one of a series of documents regarding the use of X.509 certificates in metadata. The following instructions are intended for an InCommon Federation participants wishing participant who wishes to replace an old certificate with a new certificate in metadata. Such a migration process (or key rollover, as it is sometimes called) is required, for example, in the case of expired certificatesto replace an expiring certificate.
|Table of Contents|
Wait 1–14 While we strongly recommend all participants refresh their metadata daily, things happen. Allow for up to 14 days for new metadata to propagate throughout the InCommon Federation.