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

Issue 632728 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Enable chrome.certificateProvider API on the login screen

Project Member Reported by emaxx@chromium.org, Jul 29 2016

Issue description

The chrome.certificateProvider API is currently disabled for the signin profile.

It should be enabled in order to support the "Extended Login" project (e.g. using the smart cards for authentication).
 

Comment 1 by emaxx@chromium.org, Jul 29 2016

Owner: emaxx@chromium.org
Status: Started (was: Available)

Comment 2 by emaxx@chromium.org, Jul 29 2016

Cc: xiy...@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 29 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/78a03b949912a688a808c0d3624d78d82672db9f

commit 78a03b949912a688a808c0d3624d78d82672db9f
Author: emaxx <emaxx@chromium.org>
Date: Fri Jul 29 15:23:14 2016

Enable chrome.certificateProvider API on the login screen

This turns on the chrome.certificateProvider API for the login screen
apps by allowing to create the CertificateProviderService for the signin
profile.

BUG= 632728 
TEST=manual (install a smart card app on the login screen and go through SAML login with an IdP page that requires the client certificate)

Review-Url: https://codereview.chromium.org/2195533003
Cr-Commit-Position: refs/heads/master@{#408639}

[modify] https://crrev.com/78a03b949912a688a808c0d3624d78d82672db9f/chrome/browser/chromeos/certificate_provider/certificate_provider_service_factory.cc

Comment 4 by emaxx@chromium.org, Aug 29 2016

Status: Fixed (was: Started)

Comment 5 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 6 by dchan@google.com, Nov 19 2016

Labels: VerifyIn-56

Comment 7 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 8 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59
Status: Verified (was: Fixed)

Sign in to add a comment