Intent to Implement and Ship: `CredentialsContainer::preventSilentAccess` in Credential Management API

66 views
Skip to first unread message

Jan Wilken

unread,
May 19, 2017, 8:27:36 AM5/19/17
to blink-dev, Vasilii Sukhanov, Dominic Battré, Zach Koch, Mike West, Jochen Eisinger

Contact emails

jdoe...@chromium.org, vas...@chromium.org

 

Specification

https://w3c.github.io/webappsec-credential-management/

Summary

This intent renames CredentialsContainer::requireUserMediation to CredentialsContainer::preventSilentAccess in the Credential Management API.

  

Motivation

The WebAuthn API was rewritten in https://github.com/w3c/webauthn/pull/384 to extend the Credential Manager API.

One of the issues raised is that "requireUserMediation" is a poor name for their use case. Thus this new name is introduced.

Please see the correponding GitHub issue for more details: https://github.com/w3c/webappsec-credential-management/issues/74


Usage information

Usage of the Credential Manager API is low in general: https://www.chromestatus.com/metrics/feature/popularity#CredentialManagerGet


Interoperability and Compatibility Risk

Low risk, since overall usage is low and no other browser has shipped the Credential Manager API yet.

 

Alternative implementation suggestion for web developers

Instead of using requireUserMediation web developers should use preventSilentAccess instead.

 

OWP launch tracking bug

http://crbug.com/724464


Entry on the feature dashboard

https://www.chromestatus.com/feature/4781762488041472

 

Requesting approval to remove requireUserMediation?

No, complete removal is planned for M62.

 

Requesting approval to ship preventSilentAccess?

Yes.

Philip Jägenstedt

unread,
May 22, 2017, 8:47:09 AM5/22/17
to Jan Wilken, blink-dev, Vasilii Sukhanov, Dominic Battré, Zach Koch, Mike West, Jochen Eisinger
This is similar to Intent to Implement and Ship: `mediation` enum argument to `CredentialsContainer::get()` in Credential Manager API

https://github.com/w3c/webappsec-credential-management/pull/84 is still open, but LGTM1 to whatever this ends up being renamed to, as long as the spec is changed before the code change lands.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0a72349a-b071-434c-8744-49cabb26cfa6%40chromium.org.

TAMURA, Kent

unread,
May 22, 2017, 11:19:25 PM5/22/17
to Philip Jägenstedt, Jan Wilken, blink-dev, Vasilii Sukhanov, Dominic Battré, Zach Koch, Mike West, Jochen Eisinger
LGTM2


Rick Byers

unread,
May 24, 2017, 11:30:06 PM5/24/17
to TAMURA, Kent, Philip Jägenstedt, Jan Wilken, blink-dev, Vasilii Sukhanov, Dominic Battré, Zach Koch, Mike West, Jochen Eisinger
Reply all
Reply to author
Forward
0 new messages