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: Huge Progress by the Community

Nov 28, 2018, by Albert Wu
Tags: Frontpage News, InCommon, Recent Posts, Trust & Identity

On December 14, 2018, the InCommon Baseline Expectations for Trust in Federation will become mandatory for all Federation participants. This marks a significant milestone as the community moves to improve trust and interoperability.

Rallying all participants to meet Baseline Expectations requirements has been a tremendous collaborative effort, led by the InCommon Community Assurance and Trust Board (CTAB). Thanks to CTAB and strong efforts by the community, we are nearly there.

Baseline Expectations provides a set of policy and operational requirement for all InCommon Federation participants. It establishes a baseline for trust, promotes more predictable collaboration, better user experience, and continues to grow the InCommon Federation’s strategic value to research and education (Baseline Expectations for Trust in Federation: Increasing Trust and Interoperability in InCommon). 

Jim Blasney social media post

In February 2018, when this effort started, only 16% of identity providers and 5% of service providers met Baseline Expectations. As of November 30, that number has grown to 84% of identity providers and 59% of service providers. All told, 78% of InCommon participant organizations now meet the requirements. The following charts illustrate our progress to date:

Line graph illustrating percentage meeting baseline

Graph illustrating percentage meeting baseline expectations

The CTAB and InCommon operations have provided a series of webinars, monthly informational metadata “health checks” (recently moving to biweekly), and a series of “office hours” to answer community members’ specific questions. In addition, the latest version of the InCommon Federation Manager now supports a bulk update feature to help organizations with a large number of registered records to make it easier to do a mass change to their information. 

What’s next? Organizations that have not met the deadline can request an extension for up to 90 days. After that, a Community Dispute Resolution Process kicks in. Dispute resolution proceeds in escalating stages, starting with an informal and lightweight method, and progressing to further formality and rigor where needed.