bas-federation-structure October 2026
Norlander Informational [Page]
Published:
Author:
H. Norlander
The Swedish Agency for Digital Government (Digg)

BAS: OpenID Federation Structure 1.0 – draft 01

Abstract

BAS is a federation for API access based on OAuth 2.0. It is built on OpenID Federation [OpenID.Federation] and profiled by the "Swedish OpenID Federation Deployment and Interoperability Profile" [OIDC.Sweden.Federation]. BAS declares federation rules and policies in "BAS: Federation Rules and Policies 1.0" [BAS.Rules]. This document describes the BAS OpenID Federation structure, including the federation services provided by the Federation Operator and by the Federation Registration Operators, and provides connection information for participating parties.

Registration Number

TODO

▲

Table of Contents

1. Introduction

BAS is a federation for API access based on OAuth 2.0, in which the Swedish Agency for Digital Government (Digg) is the Federation Operator. It connects organizations that offer APIs and other protected resources with organizations whose services need to call them, so that a Client can obtain an access token from an Authorization Server and use it at a Protected Resource, with BAS providing the metadata the parties need to establish contact with each other. Organizations join BAS through a Federation Registration Operator, which verifies the organization and registers its Entities in the federation.

The federation is built upon OpenID Federation 1.0 [OpenID.Federation], and profiled by the "Swedish OpenID Federation Deployment and Interoperability Profile" [OIDC.Sweden.Federation]. OAuth 2.0 within BAS follows the "Ena OAuth 2.0 Interoperability Profile" [Ena.OAuth2]. BAS declares federation rules and policies in "BAS: Federation Rules and Policies 1.0" [BAS.Rules].

OpenID Federation gives the federation a common root of trust, the Trust Anchor, whose federation key every participant configures. Starting from that root, trust in an individual Entity is established by collecting and validating a chain of signed Entity Statements, and the metadata that a participant needs in order to interact with that Entity is carried in the same chain.

Registering an Entity in the Production or QA environments requires that the organization has a contract or an agreement with Digg. The Sandbox environment carries no such requirement, and is open to any organization that wants to test or develop against the federation

Federation Structure describes the roles in BAS and the federation services each role provides: the Federation Operator (Digg) provides the Trust Anchor and its resolver, and each Federation Registration Operator provides a Federation Registration Entity through which Federation Members register their Entities. How an organization joins BAS as a Federation Registration Operator or as a Federation Member is described in Joining the Federation. Finally, BAS Federation Environments gives the Entity Identifiers, endpoints, and Trust Anchor keys for each of the environments.

1.1. Terminology

This document uses the terms "Client" and "Authorization Server" as defined by The OAuth 2.0 Authorization Framework [RFC6749], the term "Protected Resource" as defined by The OAuth 2.0 Authorization Framework: Bearer Token Usage [RFC6750], the terms "Entity", "Entity Configuration", "Entity Identifier", "Subordinate Statement", "Intermediate Entity", "Leaf Entity", "Trust Anchor", "Trust Chain" and "Resolved Metadata" defined in OpenID Federation 1.0 [OpenID.Federation], and the terms "Federation Registration Entity" and "Federation Protocol Entity" defined in the Swedish OpenID Federation Deployment and Interoperability Profile [OIDC.Sweden.Federation]. The terms "Federation Operator", "Federation Registration Operator" (anslutningsoperatör), "Federation Member" (federationsmedlem) and "Federation Registration Entity" (anslutningstjänst), as used within BAS, are defined in BAS: Federation Rules and Policies 1.0 [BAS.Rules].

2. Federation Structure

System Access Trust Anchor

The Trust Anchor is the root of the federation and is operated by Digg as the Federation Operator. Participants within the federation configure trust to the federation by trusting the Trust Anchor federation key, see BAS Federation Environments below. In the Subordinate Statement it issues for each Federation Registration Entity.

Resolver

The Trust Anchor exposes a resolve endpoint for resolving the metadata of Entities in the federation, according to Section 8.3 of [OpenID.Federation].

Federation Registration Entity

An Intermediate Entity operated by a Federation Registration Operator, through which the operator registers the Entities of Federation Members. There is one Federation Registration Entity per Federation Registration Operator, so their number grows as operators join. It issues Subordinate Statements for the Entities it registers, pins the metadata values checked during registration, and applies the Registration Policies of [SIB.Registration].

Trust Mark Issuers

Trust Mark Issuers are not yet defined for BAS, see Section 5 of [BAS.Rules].

3. Joining the Federation

3.1. Joining as a Federation Registration Operator

A Federation Registration Operator contacts the Federation Operator (Digg) and registers its Federation Registration Entity with the Federation Operator.

3.2. Joining as a Federation Member

The member chooses a Federation Registration Operator and registers its Entities through that operator's Federation Registration Entity.

3.3. Updating a Registration

Changes to pinned metadata values and to Federation Entity Keys go through the Federation Registration Operator, see Section 7.3 of [BAS.Rules].

4. Trust Marks

Trust Marks are not yet defined for BAS, see Section 5 of [BAS.Rules].

5. BAS Federation Environments

5.1. Production

5.1.1. Trust Anchor

Table 1
Property Value
Entity Identifier https://fed.ena-infrastructure.se/trustanchor
Resolve endpoint https://fed.ena-infrastructure.se/trustanchor/resolve
Trust Anchor Federation Key To be added (PEM and JWK)

5.1.2. Federation Registration Entities

Table 2
Federation Registration Operator Entity Identifier Registration interface

5.2. QA

5.2.1. Trust Anchor

Table 3
Property Value
Entity Identifier https://qa.fed.ena-infrastructure.se/trustanchor
Resolve endpoint https://qa.fed.ena-infrastructure.se/trustanchor/resolve
Trust Anchor Federation Key To be added (PEM and JWK)

5.3. Sandbox

5.3.1. Trust Anchor

Table 4
Property Value
Entity Identifier https://fed.sandbox.ena-infrastructure.se/trustanchor
Resolve endpoint https://fed.sandbox.ena-infrastructure.se/trustanchor/resolve
Trust Anchor Federation Key To be added (PEM and JWK)

6. Normative References

[BAS.Rules]
Norlander, H., "BAS: Federation Rules and Policies 1.0, draft 01", .
[Ena.OAuth2]
Lindström, M., "Ena OAuth 2.0 Interoperability Profile 1.0, draft 01", , <https://ena-infrastructure.github.io/specifications/ena-oauth2-profile.html>.
[OIDC.Sweden.Federation]
Lindström, M. and S. Santesson, "Swedish OpenID Federation Deployment and Interoperability Profile 1.0", , <https://www.oidc.se/specifications/swedish-openid-federation-profile.html>.
[OpenID.Federation]
Hedberg, R., Jones, M.B., Solberg, A., Bradley, J., De Marco, G., and V. Dzhuvinov, "OpenID Federation 1.0", , <https://openid.net/specs/openid-federation-1_0.html>.
[RFC6749]
Hardt, D., Ed., "The OAuth 2.0 Authorization Framework", RFC 6749, DOI 10.17487/RFC6749, , <https://www.rfc-editor.org/info/rfc6749>.
[RFC6750]
Jones, M. and D. Hardt, "The OAuth 2.0 Authorization Framework: Bearer Token Usage", RFC 6750, DOI 10.17487/RFC6750, , <https://www.rfc-editor.org/info/rfc6750>.
[SIB.Registration]
TODO, "Registration: application requirements and guidance (Registrering – Tillämpningskrav och vägledning), version 13".

Appendix A. Notices

Copyright (c) The Swedish Agency for Digital Government (Digg), 2026. All Rights Reserved.

Appendix B. Document History

1.0 - draft 01
Initial version.

Author's Address

Henric Norlander
The Swedish Agency for Digital Government (Digg)