My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 166: Failure when client certificate is requested
33 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  wtc@chromium.org
Closed:  Mar 2009

Restricted
  • Only users with Commit permission may comment.


Sign in to add a comment
 
Reported by billharr...@gmail.com, Sep 2, 2008
Product Version      : <see about:version>
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3:
    Firefox 3: OK
IE 7:

What steps will reproduce the problem?
1. Open site that requests a client certificate
2. Error 110 appears
3.

What is the expected result?
Allow the user to continue if client certificate cannot be presented.  In 
this case, the web application will fall back to password authentication 
with Firefox and IE.

What happens instead?

Error 110 (see attached).  No way to continue.

Please provide any additional information below. Attach a screenshot if 
possible.


chrome_error_110.jpg
18.7 KB   View   Download
Sep 2, 2008
#1 james.a....@gmail.com
This is likely related to  issue 148 
Sep 3, 2008
#2 badfre...@gmail.com
I had a similar problem. When I went to page that needs smart card certificate, 
Chrome missed first window where I have to input PIN of smart card and went directly 
to password window. Therefore, it looked like smart card is not in the reader.

No 'Error 110' reported, just didn't work.
Sep 4, 2008
#3 wtc@chromium.org
In the current implementation based on WinHTTP, Chrome supports
sites that request but don't require SSL client authentication
only on Windows Vista, because the WINHTTP_NO_CLIENT_CERT_CONTEXT
flag is not supported on Windows XP:
http://msdn.microsoft.com/en-us/library/aa384066(VS.85).aspx

This limitation of WinHTTP will be eliminated when we finish and
switch to our new HTTP stack.

We also need to implement the UI for the selection of a client
certificates, when the user does have client certificates.  That
work can proceed in parallel to the work on the new HTTP stack.
Status: Untriaged
Owner: w...@chromium.org
Labels: -OS-All -Area-Unknown OS-Windows Area-BrowserBackend
Oct 22, 2008
#4 mal.chromium@gmail.com
(No comment was entered for this change.)
Status: Assigned
Labels: Mstone-1.1 NewHTTP
Dec 3, 2008
#5 niran...@chromium.org
 Issue 5030  has been merged into this issue.
Dec 17, 2008
#6 wtc@chromium.org
 Issue 5602  has been merged into this issue.
Jan 12, 2009
#7 lafo...@chromium.org
(No comment was entered for this change.)
Labels: Mstone-2.0
Mar 11, 2009
#8 wtc@chromium.org
This bug has been fixed in the Dev channel 2.0.x.x releases.
Note that SSL client certificate support is  issue 318 .  This
bug is about supporting sites that request but don't require
SSL client certificates.

In the Stable channel 1.0.154.x releases, this bug is only
affecting users on Windows XP SP2.  Users on Windows XP SP3
or Vista are not affected.
Status: Fixed
Dec 18, 2009
#9 mal.chromium@gmail.com
(No comment was entered for this change.)
Labels: -Area-BrowserBackend Area-Internals Internals-Network
Jul 31, 2010
#10 vmpin...@gmail.com
browser=true
Oct 11, 2012
#11 bugdro...@chromium.org
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Labels: Restrict-AddIssueComment-Commit
Mar 10, 2013
#12 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-Internals -Internals-Network Cr-Internals Cr-Internals-Network
Sign in to add a comment

Powered by Google Project Hosting