-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: Wallet Instance Attestation #14
feat: Wallet Instance Attestation #14
Conversation
…com/italia/eidas-it-wallet-docs into wallet-instance-attestation-SIW-151
Co-authored-by: Giuseppe De Marco <giuseppe.demarco@teamdigitale.governo.it>
|
||
- **Message 1**: The User initializes the Wallet Instance. | ||
In particular, this process happens when the mobile application | ||
is launched and every time the User wants to request or present |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When it is launched the first time after the installation and when it is expired. During the request or the presentation is under discussion. We have to take into account also the flows in presence and when the wallet instance does not have the connection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So how can we rephrase this sentence for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fmarino-ipzs please provide a suggestion to be committed
|| || client-assertion-type: | | ||
|| || ``jwt-key-attestation``. | | ||
+------------------------------------+------------------------------------+ | ||
|| token_endpoint_auth_methods_suppo || Supported authentication method | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we must define what exactly is the supported client authentication method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|| rted || for the endpoint token. | | ||
|| || | | ||
+------------------------------------+------------------------------------+ | ||
|| token_endpoint_auth_signing_alg_v || List of supported signature | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Depending on the supported client authentication mechanism we must have this parameter.
- **Message 4**: The Wallet Instance verifies that the Wallet Provider is | ||
trustworthy by resolving the provider's trust chain up to the anchor | ||
- **Message 5-7**: The Wallet Instance instantiates a new key pair on its TEE | ||
and requests a ``nonce`` from the Wallet Provider (as a measure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I agree
- **Message 4**: The Wallet Instance verifies that the Wallet Provider is | ||
trustworthy by resolving the provider's trust chain up to the anchor | ||
- **Message 5-7**: The Wallet Instance instantiates a new key pair on its TEE | ||
and requests a ``nonce`` from the Wallet Provider (as a measure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The nonce
parameter could be useful for Integrity API flow.
Co-authored-by: fmarino-ipzs <77629526+fmarino-ipzs@users.noreply.github.com>
Wallet Instance Attestation
This PR adds the design review of the
Wallet Instance Attestation
including the request flow and format of theWallet Instance Attestation Request
andWallet Provider Entity Configuration
resolve #4