...
The fallback metadata aggregate comes into play when introducing a breaking change into InCommon metadata (such as SHA-2). When a change is made to the production metadata aggregate, and that change breaks a metadata process, the affected deployment can temporarily migrate to the fallback metadata aggregate. This gives the deployment time to adjust to the breaking change.
In the case of SHA-2, deployments have approximately three months (beyond the March 29 milestone) to become compatible with SHA-2. At that time, the fallback metadata aggregate will be synced with the production metadata, which forces all deployments to conform.
| Note | ||
|---|---|---|
| ||
All deployments should migrate to the new production metadata aggregate ASAP but no later than June 30, 2014. From that day forward, all InCommon metadata aggregates will be signed using a SHA-2 digest algorithm. |
Questions about SAML Software
...