Docs
The profile's contracts, layer by layer and in reading order. Each one is an OpenAPI document, rendered here and downloadable from its view. The reason behind each decision is not in the contract: it is in the essays.
The contracts, their rendered views and the essays are written in Spanish.
Contracts
Layer 2 · Authentication, consent and authorization
-
01
Consent Draft
Consent as a resource with its own state: creating, querying and revoking it, and notifying the other side of a revocation.
-
02
Authorization Draft
The surface of a transmitter's authorization server as the profile requires it: discovery metadata with the mandatory values, PAR, authorization, token, introspection and revocation, and the
pafa:consentauthorization_detailstype that binds the token to the consent.
How to read them
-
What a contract is
A self-contained OpenAPI 3.0 of its own: no external references, no build. It fixes the paths, fields and values a conforming implementation has to respect.
-
Where the why is
Each contract makes the decisions of an essay implementable. The contract says what; the essay says why, and with which precedents.
-
How it changes
«Draft» means written and implementable, not ratified: fields and names may change before a 1.0. Every change goes in the changelog with its reason.