Reading Time: < 1 minute
Banner Image

Baseline Expectations
for Trust in Federation Overview

Working together to create trusted and reliable collaborations

The InCommon community has adopted the Baseline Expectations for Trust in Federation to improve interoperability.

ed by the InCommon Community Trust and Assurance Board, the community determined that a set of common expectations that all participants meet will

  • provide a baseline for trust
  • make collaboration more predictable
  • ensure that the InCommon Federation’s strategic value to research and education continues to grow

The Baseline Expectations for Trust in Federation are comprised of three brief sets of statements for: Identity Provider Operators (IdP), Service Provider Operators (SP), and the Federation Operator.

Evolving via consensus

The community drives the process of evolving and clarifying the Baseline Expectations, led by the InCommon Community Trust and Assurance Board (CTAB).

A futuristic photo illustration streaming lights.

Resolving disputes

Undoubtedly there will be cases of dispute – for example, when a participant believes that another organization’s operations do not meet Baseline Expectations. The Baseline Expectations include a dispute resolution process to resolve disagreements.

The man

Intent to alter metadata

As the federation operator, InCommon also has responsibilities under Baseline Expectations. For example, InCommon has several processes to ensure that Participants’ federation metadata is accurate. Part of the documentation is a process that InCommon will use before it alters metadata.

Baseline Expectations Banner