New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 756801 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Credential Manager API - storing a Credential with insecure iconURL doesn't result in rejected promise.

Project Member Reported by tgarbus@google.com, Aug 18 2017

Issue description

Chrome Version: 60.0.3112.90 (Official Build) (64-bit)
OS: Mac OS X

What steps will reproduce the problem?
Run the following from JS:
(1) f = new FederatedCredential({ id: "id", provider: "https://example.com", iconURL: "http://example.com/", name: "name" })
(2) p = navigator.credentials.store(f)
(3) p // if running from DevTools to look up value of p

What is the expected result?
Note that iconURL is a "http://" not "https://" URL.
Promise should be rejected. According to the spec, iconURL must be a secure URL. See: https://w3c.github.io/webappsec-credential-management/#credentialuserdata-mixin

What happens instead?
Promise is resolved.
 
The promise is resolved but what happens to the credential? Is it stored?

Comment 2 by tgarbus@google.com, Aug 21 2017

Just checked - it is indeed stored.
Status: Fixed (was: Untriaged)

Sign in to add a comment