Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Verifying an Entity's identity and organizational connection involves two kinds of rules. What the organizational connection means, how a Registration Intermediate establishes it, and how a presentation name is checked, is stated in Requirements and Guidance for Verification of Organisational Affiliation Affiliation (Swedish: Tillämpningskrav och vägledning för verifiering av organisationskoppling) and Requirements and Requirements and Guidance for Verification of Display Name Name (Swedish: Tillämpningskrav och vägledning för verifiering av visningsnamn).  This This document states how the outcome of those checks is expressed in metadata, so that a peer can read it. The documents are meant to be read together. A metadata value assigned under this specification carries exactly the meaning given to it by the corresponding tillämpningskravrequirement, and no other.

The protocol requirements build on [Ena.OAuth2], which is the OAuth 2.0 profile that BAS applies. Entities in BAS adhere to that profile, and this document restates its metadata requirements at the levels it gives, adding the constraints that follow from operating in a federation. This is the current scope rather than a permanent limitation. BAS may later admit other Entity Types, and Entities adhering to other profiles, and the requirements in this document would then not apply to them unaltered.

...