Overview
As per the European Digital Identity Wallet Architecture and Reference Framework Trust Model,
- Relying Parties are registered by a Relying Party Registrar in their Member State.
- As a result of the registration, a Relying Party receives an access certificate (WRPAC) from a Relying Party Access CA and a registration certificate (WRPRC).
- The RP access certificate is used by the Wallet Instance to authenticate the Relying Party Instance.
- The RP registration certificate is used by the Wallet Instance to access the intended use and attribute access policies of a WRP.
- Relying Party authentication is a process whereby a Relying Party proves its identity to a Wallet Instance, in the context of a transaction in which the Relying Party requests the Wallet Instance to release some attributes.
- Relying Party authentication is included in the protocol used (both in ISO/IEC 18013-5 and OpenID4VP) by a Wallet Instance and a Relying Party Instance to communicate.
For more detailed information:
- Registrars
- Access Certificate Authorities
- Providers of registration certificates
- CIR 2025/848
- TS5
- TS6
The Relying Party Registration complies with the requirements set out by the CIR 2025/848, TS5 and TS6.
The RP access certificate format complies with ETSI TS 119 411-8.
The RP registration certificate format complies with ETSI TS 119 475.
The Relying Party Registration Service provides two main functionalities:
- Register a new Relying Party, issuing the Relying Party Access certificate and keypair in pkcs#12 (P12) format and Registration certificate in JSON Web Tokens (JWT) and CBOR Web Tokens (CWT) format, both signed with an Advanced Electronic Signature (ADES) with the B-B profile.
- List the certificates issued and enable their revocation.
For more information, please refer to the Relying Party Registration service repository.
Recommended Workflow
The Relying Party Registration service follows a specific workflow for registering new relying parties and managing their certificates.
For more information, please refer to the Relying Party Registration Workflow and Endpoints.
Swagger Documentation
Full API documentation is available through Swagger UI.
/swagger/