BoB Participant Metadata API provides en interface for participants to manage metadata coordinated by Administering Body (AB).
The API uses Proof-of-possession authorization tokens (POP) as described in MTS5. Key management for the POP keys themselves are not included in the API.
References: Coordination and key management is documented in MTS4. POP tokens are documented in MTS5.
getParticpantMetadataFile
Get the latest participant metadata file, signed using JSON Web Signature (JWS) as defined in (RFC 7515). Metadata validity is specified in the JWS header.
getParticipantMetadata
Get participant metadata for a specific participant.
*DomainName
The participant domain name can be get/updated/deleted via the following calls. A single domain name can be associated with each participant. The domain name is used for dynamic key fetching via DNS (MTS1 section 2.4).
- getDomainName
- updateDomainName
- deleteDomainName
*MtbPublicKey
The current MTB signing keys can be get/added/deleted via the following calls. One should not existing keys are immutable and can only be deleted.
- getMtbPublicKeys
- addMtbPublicKey
- getMtbPublicKey
- deleteMtbPublicKey
*AuthtokenPublicKeys
The current authentication token signing keys can be get/added/deleted via the following calls. One should not existing keys are immutable and can only be deleted.
- getAuthtokenPublicKeys
- addAuthtokenPublicKey
- getAuthtokenPublicKey
- deleteAuthtokenPublicKey
*InterfaceEndpoints
Interface endpoints can be get/added/updated/deleted via the following calls.
- getInterfaceEndpoints
- addInterfaceEndpoint
- getInterfaceEndpoint
- updateInterfaceEndpoint
- deleteInterfaceEndpoint
*IssuerSignatureConstraint
- getIssuerSignatureConstraint
- addIssuerSignatureConstraint
- updateIssuerSignatureConstraint
- deleteIssuerSignatureConstraint