Internet2

close
Use Internet2 SiteID

Already have an Internet2 SiteID?
Sign in here.

Internet2 SiteID

Your organization not listed? Create a local account to use Internet2 services.

Create SiteID

Blogs

Baseline Expectations - Who Meets the Metadata Expectations?

Sep 19, 2018, by Dean Woodbeck
Tags: Trust & Identity

InCommon participants have made substantial progress in meeting Baseline Expectations for Trust in Federation. Seventy-five percent of Identity Providers and almost half of Service Providers now meet the metadata elements of the program. 

A wiki page includes a complete list of all InCommon participants and the status of their entities, in terms of meeting Baseline. The list shows you the number of entities deployed by each organization and how many meet or do not meet the Baseline metadata element. 

The InCommon Community Trust and Assurance Board (CTAB) and InCommon staff are assessing any common barriers to meeting the metadata expectations. The two metadata elements with the lowest percentage are a logo URL and a privacy URL. The CTAB has provided guidance in both areas, and is discussing other ways to help participants meet these expectations.

InCommon operations continues to send monthly metadata health checks, which go to organizations with incomplete entities in metadata. The monthly health checks look for these items in metadata:

  • Logo URL
  • Privacy URL
  • Technical Contact
  • Security Contact
  • Administrative Contact

This graph shows the percentage of Identity Providers and Service Providers meeting all Baseline Expectations metadata requirements.

Click on Image to view larger version

Click on Image to view larger version

 


This graph shows the percentage of participants (IdPs and SPs) meeting individual Baseline Expectations elements in metadata.

Click on Image to view larger version

Click on Image to view larger version