Issue metadata
Sign in to add a comment
|
Not showing "Select a certificate" popup on XHR request
Reported by
ii.hsif....@gmail.com,
Nov 29
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3622.0 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Access a web site which invokes cross origin XHR access requiring SSL client certificate. 2. Invoke the request. 3. The request fails with "net::ERR_SSL_CLIENT_AUTH_CERT_NEEDED" What is the expected behavior? Before 72.0.3622.0, chrome popups "Select a certificate" even when cross origin XHR request is involved, and it should. What went wrong? There is no way to select an appropriate client certificate other than to enter and open the URL of XHR request in URL bar. Did this work before? Yes 72.0.3610.2 Chrome version: 72.0.3622.0 Channel: dev OS Version: OS X 10.14.1 Flash Version:
,
Nov 30
Thanks for filing the issue... @reporter: Could you please provide sample URL that reproduces the issue so that it would be really helpful in triaging the issue.
,
Dec 3
,
Dec 5
Not sure if CORS is at all relevant here, though leaving the label, just in case Adam knows something I don't.
,
Dec 5
Can you include the variations from chrome://variations ?
,
Dec 6
,
Dec 6
Adding back CORS. The issue is that Chrome 'used' to violate the CORS spec by sending client certs on anonymous requests (and may have involved prompting). It's unclear whether this was intentional change in spec conformance or something else.
,
Dec 7
It's also possible that the same thing is affecting b/120149384 (on an internal Google site). A net log has been provided on that bug thread.
,
Dec 14
Please include a NetLog as per https://www.chromium.org/for-testers/providing-network-details
,
Dec 20
I built a test server that always requires a client cert (but will accept any), and on requests to /xhr_test will send an Access-Control-Allow-Origin header with value *. On a separate origin (scheme was file - I didn't bother spinning up a webserver), I loaded a page that made an XHR request to that endpoint. In both 72.0.3610.2 and 72.0.3622.0 (debug builds, fresh profiles), I got the certificate selector pop-up, and the XHR was successful. I tested 72.0.3622.0 with the network service enabled and disabled. I searched through the git log of revisions between 72.0.3610.2 and 72.0.3622.0 for "cert" to see if there's anything obvious that might affect this. https://chromium-review.googlesource.com/c/chromium/src/+/1290435 is related to client certs, but without a repro I don't know whether it's related to this issue.
,
Jan 11
OP: Please include a net log as per comment #9 or we'll have to close this bug.
,
Jan 17
(5 days ago)
Archived due to lack of activity. Please feel free to reopen when you have net logs collected which is requested in comment #9. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Nov 30