New chrome.certificateProvider.requestPIN method |
||||||
Issue descriptionSmart card PIN requests are currently handled by 3rd party middleware apps (they draw the UI and handle the user input). We want to switch this to a system level call to be able to properly integrate smart card use into the various Chrome OS screens. The different surfaces involved each need separate UI treatment of a PIN request. ** User sessions ** Lock screen ** Login screen ** Pods screen ** Kiosk mode This is the parent bug tracking these various surfaces.
,
May 18 2016
,
May 18 2016
The API 1. Should draw a PIN entry dialog. 2. Should show the name of the app requesting the PIN (as well as a link to the webstore entry). 3. Dialog should contain OK and Cancel buttons. 4. API can afford PIN retries and must handle UI accordingly. 5. Can show error messages coming from middleware apps (e.g. 2 attempts remaining).
,
May 18 2016
The implementation should keep in mind that the UI treatment will differ depending on the context the code is running in i.e. kiosk, login screen, etc.
,
Jul 6 2016
Have there been any UX mocks created for an example use case? I am concerned about creating a UI dialog that becomes difficult to maintain, especially if this is intended to be able to work from the login screen and from lock screens, not to mention kiosk mode. Is this something we could build into the Message Center instead?
,
Jul 7 2016
We have outlines the way UI will look like in a doc: https://docs.google.com/document/d/1tRUkeMFGqyNU8meuJWRday08YbOusB2ZerJLwd-5NL4/edit
,
Jul 7 2016
We've also gone through UI review with both Jenn and Zel. I added you to the UI approval thread.
,
Jul 28 2016
,
Jul 29 2016
,
Dec 5 2016
I tested manually the implementation added in issue 612886 on the login screen - looks like everything is working correctly.
,
Dec 5 2016
,
Feb 27 2017
Marking as verified based on #c10. Please reopen if you see any issues |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dskaram@chromium.org
, May 18 2016