Refactor the CredentialManagement API mojo and dispatch logic |
||||||
Issue descriptionExtract the disambiguation logic from //components/password_manager into an intermediary layer in the browser that picks the backend and sends off requests to the password store or the webauthn layer. Refactor the WebAuthN mojo pipe into the CredentialManager mojo pipe.
,
Jun 27 2017
,
Mar 31 2018
This is related to Issue 762638, as it revolves around the question of how the architecture between //device/fido, //services, Blink, and //components/password_manager should ideally look like.
,
Apr 2 2018
Do we really need to keep this in the security queue. Might Restrict-View-Google be sufficient?
,
Apr 2 2018
If it needs to be in the security queue, we'll have to figure out some mandatory labels, such as: - Severity: https://www.chromium.org/developers/severity-guidelines - Impact: Stable / Beta / Head / None - OS'es that are affected + we also need to have an owner assigned. Please advise whether we make it a regular bug with Restrict-View-Google label, or provide a guidance on the points listed above. Thanks!
,
Apr 3 2018
This is a harmless refactoring, no need to put any restrictions on it. Sorry, I must have mis-clicked when triaging it.
,
Jan 9
,
Jan 16
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kpaulhamus@chromium.org
, Jun 14 2017