...
In addition, if you don't refresh your metadata regularly, it is likely that a software implementation will fail at some point since the XML document carries an expiration date (validUntil) that causes the metadata to expire in three weeks. InCommon strongly recommends that you do not rely on the actual length of this validity interval in any way, and in fact, we reserve the right to shorten the validity interval with little or no notice.
| Tip | ||
|---|---|---|
| ||
Metadata is refreshed on at least a daily basis, and a participant's federation software functionality represented by the information in the metadata reflects any updates to it. For example, the public keys in the metadata are accepted for the purposes for which they are labeled and clients are sent to the appropriate locations. Partner sites that make changes to the information in their metadata do not need to contact the participant out of band to ensure proper ongoing operations. |
Firewall Configuration
Depending on your environment, you may have to poke a hole in an outbound firewall to get metadata refesh to work. In that case, you will actually want to poke two holes in that firewall since there are two metadata servers as described below.
...