Versions Compared

Key

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

Federationskontext BAS: OAuth 2.0 Metadata Requirements 1.0, draft 01



PublishedSeptember 2026
WorkgroupSamordnad identitet och behörighet
OrganizationThe Swedish Agency for Digital Government (Digg)

Abstract

This specification defines the metadata requirements for OAuth 2.0 Clients, Authorization Servers and Protected Resources participating in Federationskontext BAS, a federation context for machine-to-machine access within the Swedish public sector. The metadata is published in Entity Configurations according to OpenID Federation 1.0. The requirements apply to the resolved metadata, meaning the metadata that results once the Trust Chain of an Entity has been applied to the declarations the Entity makes about itself. The requirements are limited to what a party needs in order to verify the system identity of an Entity and the organization it is registered for. They do not regulate the information exchange that follows.

Table of Contents

  1. Introduction 1.1. Requirements Notation and Conventions 1.2. Terminology 1.3. Scope of the Requirements
  2. General Requirements
  3. Common Requirements 3.1. The organization_identifier Format 3.2. Protocol Keys
  4. OAuth Client Requirements 4.1. Client Identifier 4.2. Client Authentication
  5. Authorization Server Requirements
  6. Protected Resource Requirements 6.1. Resource Identifier
  7. BAS Metadata Policies 7.1. Trust Anchor Metadata Policy 7.2. Registration Intermediate Metadata Assignment
  8. Normative References
  9. Informative References

Appendix A. Notices Appendix B. Document History

...

1. Introduction

This document specifies the metadata that an OAuth 2.0 Client, Authorization Server or Protected Resource publishes when it joins Federationskontext BAS, hereafter BAS. It is written for the organizations that operate such Entities, and for the developers and operators who implement them. How BAS is structured, and how an Entity is registered in it, is described in [BAS.Rules].

...

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 [in Requirements and Guidance for Verification of Organisational Affiliation
(Swedish: Tillämpningskrav och vägledning för verifiering av organisationskoppling] and [) and Requirements and Guidance for Verification of Display 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ämpningskrav, and no other.

...

The requirement chapters state what has to appear in the resolved metadata of an Entity. Common Requirements covers the parameters that all three Entity Types share and that express identity and organizational connection. These requirements do not depend on the choices made for BAS, and are specified so that they can be applied unaltered in other federation contexts. The chapters on Clients, Authorization Servers and Protected Resources contain the requirements that are specific to BAS. BAS Metadata Policies shows how the requirements are enforced, through the metadata policy that the BAS Trust Anchor applies to every Entity, and through the per-Entity values that a Registration Intermediate sets when an Entity joins the federation. Within BAS these two roles are held by different organizations, and the document states for every assigned or constrained value which of them controls it.

1.1. Requirements Notation and Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

1.2. Terminology

This specification uses the terms "Entity", "Entity Configuration", "Entity Identifier", "Entity Type Identifier", "Intermediate Entity", "Leaf Entity", "Subordinate Statement", "Trust Anchor", "Trust Chain" and "Resolved Metadata" as defined in [OpenID.Federation], and the terms "Federation Protocol Entity" and "Federation Registration Entity" as defined in [OIDC.Sweden.Federation]. It uses the terms "Client", "Authorization Server" and "Protected Resource" as defined in [Ena.OAuth2].

...

Federation Registration Operator (Swedish: Anslutningsoperatör) : An organization that connects Federation Members to BAS and registers their Entities.

1.3. Scope of the Requirements

The requirements in this document serve one function: that a party can verify who it is about to exchange information with. To that end, this document regulates

...