
BAS is a federation for API access based on OAuth 2.0. It is built on OpenID Federation and profiled by the Swedish OpenID Federation Deployment and Interoperability Profile. The OAuth 2.0 protocol itself follows the Ena OAuth 2.0 Interoperability Profile.
The specifications below together describe how the BAS federation is governed, how it is structured, and what OAuth 2.0 Clients, Authorization Servers and Protected Resources must fulfil to participate. A suggested reading order is the rules first, then the structure, followed by the metadata and security requirements.
These are working drafts generated from the main branch.
They may change at any time and should not be considered final.
The rules and policies of the BAS federation: the roles of the Federation Operator and Federation Registration Operators, collaboration contexts, federation endpoints, entity statements and trust chains.
The structure of the federation and the services it provides, how to join as a Federation Registration Operator or Federation Member, trust marks, and connection information for the production, QA and sandbox environments.
Metadata requirements for OAuth 2.0 Clients, Authorization Servers and Protected Resources, as published in Entity Configurations and applied to the resolved metadata of each entity.
Security requirements for participants, covering transport protection, client authentication, keys, signature algorithms and key rollover. Read together with the metadata requirements.