Interfederation Technical Policy Rules
Metadata Import Policy
Global metadata is imported directly into the main production aggregate.
For the v9 deployment of the metadata aggregator (released 2019-03-20), the following import rules will be implemented (in order):
- Silently remove all imported entities with XML attribute
- Entities so marked must come from primary sources only.
- Remove (and log the removal of) the following XML elements (not entities):
<mdui:Logo> elements (not entities) with a URL that is not HTTPS-protected
- Silently remove the following XML elements (not entities):
- all MDUI metadata (e.g.,
mdui:UIInfo elements) within
- all entity attributes on the Entity Attribute Blacklist (see subsection below).
- all extended XML elements and attributes defined in namespaces not on the XML Namespace Whitelist (see subsection below).
- Remove (and log the removal of) all imported entities matching one or more of the following conditions:
- Entities with an entityID that does not begin with one of the following prefixes: “
- Entities with weak keys (which includes all keys less than 2048-bits in length)
- The use of weak keys in metadata has security and privacy implications.
- There are no weak keys in InCommon metadata and so we'd like to keep it that way.
- IdP entities with a faulty
- Require regexp attribute on
- Values which do not represent a permissible scope:
regexp="false" scope values must:
- be syntactically valid domain names (for example, they may not be empty or contain white space), and
- must represent domains under a "public suffix" such as
.edu listed in the public suffix list
regexp="true" scope values must:
- not be empty or include white space, and
- must end with:
- an escaped dot ('
- followed by a "literal tail", which must:
- consist of at least two domain labels (e.g., "
edu") separated by encoded dots ('
- which when the encoded dots are decoded represents a domain name under a "public suffix" such as
.edu listed in the public suffix list
- followed by a '
- IdP entities that do not have a SAML2 SingleSignOnService endpoint that supports the HTTP-Redirect binding.
- In effect, all imported IdPs must support SAML2.
- SP entities that do not have at least one SAML2 AssertionConsumerService endpoint that supports the HTTP-POST binding.
- In effect, all imported SPs must support SAML2.
- Entities containing literal CR characters.
- Entities containing misplaced or duplicated
- Entities containing XML failing schema validation.
- Entities that do not conform to the SAML v2.0 Metadata Profile for Algorithm Support Version 1.0
- Entities that do not follow standard rules regarding Binding values on protocol endpoints in metadata
- Entities that do not conform to the SAML V2.0 Holder-of-Key Web Browser SSO Profile Version 1.0
- Entities that do not conform to the Identity Provider Discovery Service Protocol and Profile
- Entities that do not conform to the Service Provider Request Initiation Protocol and Profile Version 1.0
- Entities that do not conform to the SAML V2.0 Metadata Interoperability Profile
- Entities that do not conform to the SAML V2.0 Metadata Extensions for Registration and Publication Information Version 1.0
- Entities that do not conform to the SAML V2.0 Metadata Extensions for Login and Discovery User Interface Version 1.0
- Entities that do not conform to the REFEDS Research and Scholarship Entity Category
- Entities that do not conform to the REFEDS SIRTFI specification
- Entities that do not conform to the SAML V2.0 Metadata specification
- SP entities with an endpoint location that is not HTTPS-protected
- Entities that do not conform to the ADFS Metadata Profile
- Entities that have inconsistent metadata for SAML 1.x support
- Entities that have errors in their
- Silently remove all imported entities that have the same entityID as an existing entity in the InCommon aggregate.
- This happens because some SPs choose to join multiple federations.
- Dozens of global SPs are filtered by this rule.
A number of additional rules are applied to ensure metadata correctness. Some common minor errors are corrected but entities failing checks such as XML schema validity are removed.
Log all of the following:
View the published import filter logs
- entities filtered by an import rule
- entities removed for lack of schema validity
- entities modified in any way
Entity Attribute Blacklist
XML Namespace Whitelist
Metadata Export Policy
Basic Metadata Export Policy
InCommon Operations refreshes the export aggregate daily, in conjunction with the daily metadata-signing process.
- IdPs are exported by default (but may choose to opt out)
- SPs actively opt in to the export process
InCommon Operations reserves the right to prevent any entity from being exported.
The following export rules have been implemented:
- Filter all entities not having XML attribute
- Only entities registered by InCommon will be exported.
- Filter the legacy incommon.org R&S entity attribute value from exported SP entity metadata:
- This legacy attribute value remains in SP metadata for backwards compatibility only. We intend to completely remove this attribute value from SP metadata in the future.
- This legacy attribute value has nothing to do with R&S interoperability outside of the InCommon Federation.
- Filter SAML1-only entities:
- An SP entity not having at least one SAML2
AssertionConsumerService endpoint that supports the HTTP-POST binding will not be exported.
- An IdP entity not having a SAML2
SingleSignOnService endpoint that supports the HTTP-Redirect binding will not be exported.
Extension schema required for exported metadata