Latest Metadata Health Check Shows Significant Progress Since February
InCommon sends monthly metadata health checks as part of the Baseline Expectations process.
InCommon sends monthly metadata health checks as part of the Baseline Expectations process. As you can see on the graphs below, more than half of Identity Providers now include all Baseline Expectations elements in their metadata, compared to 16% in February. In similar progress, 37% of Service Providers now have all elements in metadata, compared to just 5% in February.
- The metadata health checks, sent to an organization’s InCommon site admin and InCommon executive, provide feedback about whether entities have the required elements in metadata, including:
- At least one technical contact with a valid email address
- At least one administrative contact with a valid email address
- At least one security contact with a valid email address
- A valid DisplayName
- A valid HTTPS logo URL
- A valid privacy statement URL
Adding the contact information should be straightforward and the email address can be an alias (in fact, that is recommended so the email is always valid as people change roles in the organization). The InCommon Community Trust and Assurance Board (CTAB) has provided guidance for both the logo and privacy statement requirements.
Here are two graphs, which provide a snapshot of the status of things as of June 13, 2018.
The first graph shows the percentage of Identity Providers and Service Providers meeting all Baseline Expectations metadata requirements.
The second graph shows the percentage of entities meeting each Baseline Expectations element.
InCommon will continue to send monthly metadata health checks to organizations that have yet to include all Baseline Expectations elements. In July, we will publish a list of all organizations that include all of the required Baseline Expectations elements in the metadata for all of their Identity Providers and Service Providers.