AutoSelectCertificateForUrls not working on Windows
Reported by
marc.cal...@gmail.com,
Oct 19 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce the problem: 1. Specify the AutoSelectCertificateForUrls as described here http://www.chromium.org/administrators/policy-list-3#AutoSelectCertificateForUrls 2. Re-open Chrome, and open chrome://policy and verify that AutoSelectCertificateForUrls policy is enabled and status is OK. 3. Proceed to the secured site with at least one client certificate present in the certificate store. What is the expected behavior? User should not be prompted for a client certificate when AutoSelectCertificateForUrls policy is active and applies to a given site. What went wrong? I am always prompted to select a client certificate, even when I removed additional client certs and only had one. Did this work before? N/A Chrome version: 53.0.2785.143 m Channel: n/a OS Version: Server 2008 R2 Datacenter Flash Version: I tried dozens of different values for the key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\AutoSelectCertificateForUrls\1 including: {\"pattern\":\"*\",\"filter\":{}} and nothing changed the browser behavior. It may also be helpful to know that the Policy Status in chrome://policy/ was always OK.
,
Oct 20 2016
,
Oct 21 2016
Maksim, how would a customer debug his AutoSelectCerts policy? It sounds like perhaps the pattern isn't working for them.
,
Oct 21 2016
It was the escaping that was causing this to break. We can close this ticket, as these patterns worked when directly entered via regedit:
{"pattern":"*","filter":{}}
{"pattern":"abc.example.com","filter":{}}
{"pattern":"https://abc.example.com","filter":{}}
{"pattern":"*","filter":{"ISSUER":{"CN":"Remote Site Root CA"}}}
{"pattern":"abc.example.com","filter":{"ISSUER":{"CN":"Remote Site Root CA"}}}
{"pattern":"https://abc.example.com","filter":{"ISSUER":{"CN":"Remote Site Root CA"}}}
,
Nov 14 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by marc.cal...@gmail.com
, Oct 19 2016