Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Wallet Provider Backend definition term #347

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/en/defined-terms.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,9 @@ Below are the description of acronyms and definitions which are useful for furth
* - Wallet Instance
- An instance of the Wallet Solution, installed on a personal mobile device and controlled by a specific User who is its sole owner. It is the application that enables citizens to fully and autonomously manage their digital identity and EAAs.
* - Wallet Provider
- All public and/or private entities, conforming to a technical profile and registered by the Federation Authority, that provide citizens with a Wallet Solution.
- All public and/or private entities, conforming to a technical profile and accredited by the Federation Authority, that provide citizens with an IT Wallet Instance.
* - Wallet Provider Backend
- Is the technical infrastructure and server-side components, including a set of endpoints, managed by a Wallet Provider.
* - Wallet Attestation
- Verifiable Attestation, issued by the Wallet Provider, that proves the security compliace of the Wallet Instance.
* - Wallet Secure Cryptographic Device
Expand Down
4 changes: 2 additions & 2 deletions docs/en/wallet-attestation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -245,7 +245,7 @@ Below a non-normative example of the ``client_data``.

**Steps 11-12**: The Wallet Instance:
* Constructs the Wallet Attestation Request in the form of a JWT. This JWT includes the ``integrity_assertion``, ``hardware_signature``, ``challenge``, ``wallet_hardware_key_tag``, and ``public_jwk``, and is signed using the private key from the initially generated ephemeral key pair.
* Submits the Wallet Attestation Request to the Wallet Provider's backend through the token endpoint.
* Submits the Wallet Attestation Request to the token endpoint of the Wallet Provider Backend.

Below an non-normative example of the Wallet Attestation Request JWT without encoding and signature applied:

Expand Down Expand Up @@ -304,7 +304,7 @@ encoded in ``application/x-www-form-urlencoded`` format:
grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer
&assertion=eyJhbGciOiJFUzI1NiIsImtpZCI6ImtoakZWTE9nRjNHeG...

**Steps 13-17**: The Wallet Provider's backend assesses the Wallet Attestation Request and issues a Wallet Attestation, if the requirements described below are satisfied:
**Steps 13-17**: The Wallet Provider Backend assesses the Wallet Attestation Request and issues a Wallet Attestation, if the requirements described below are satisfied:

1. It MUST check the Wallet Attestation Request contains all the defined parameters according to :ref:`Table of the Wallet Attestation Request parameters <table_wallet_attestation_request_claim>`.
2. It MUST verify that the signature of the received Wallet Attestation Request is valid and associated with public ``jwk``.
Expand Down
Loading