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

Hardware Token usage consistency (by KM) #115

Open
vgalindo opened this issue Aug 18, 2016 · 1 comment
Open

Hardware Token usage consistency (by KM) #115

vgalindo opened this issue Aug 18, 2016 · 1 comment
Assignees
Labels

Comments

@vgalindo
Copy link
Collaborator

vgalindo commented Aug 18, 2016

Section 3.2: Financial Transaction Signature, with User Consent
Text: That last step requires the user to use some credentials, distributed by the bank, usually stored in a secure container, such as a hardware based token (USB token or proximity token).

Section 3.2.1: French ecosystem
Text: Without the capability to rely upon Secure Elements in the browser, banks currently face a major issue in being able to replace the existing identity scheme delegation which provides a strong authentication and signature credential

Comment: Reference to hardware based token should also include at least one example of internal hardware device such as TEE, SE, or UICC. Or alternatively, make consistent use of terms so these terms do not have to be substantiated by examples.

@sbahloul
Copy link
Collaborator

Virginie: maybe we can make a reference to the Audkenni.is / Valimo deployment in Iceland leveraging UICC ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants