Registration API changelog
0.3.0
Certificate-backed TPP consent display names
- Added
GET /tpp/{clientId}/display-nameto retrieve the name shown to users when they authorize a TPP. - Added
PUT /tpp/{clientId}/display-nameto update that name to a value backed by one of the TPP’s current certificate chains. - The consent display name is initially set from the leaf eIDAS certificate used to register the TPP, rather than the registration payload’s
namefield. POST /tpp/{clientId}/certificatesnow accepts the optionalupdateDisplayNameboolean to update the consent display name from the added certificate chain.
See Manage consent display name for request examples and complete behavior. The previous 0.2.0 Registration API specification remains available for reference.
0.2.0
- Added
DELETE /tpp/{clientId}to delete a registered client. The idempotent endpoint returns204. After deletion, the client cannot obtain access tokens and its existing tokens stop working. See Delete a client.
0.1.0
Initial release
- TPP registration, client management, and OAuth2 token endpoints
Last updated on