Bug 138216 - When a client certificate is rejected, Safari says the website didn’t accept the certificate “unknown” instead of naming the certificate
Summary: When a client certificate is rejected, Safari says the website didn’t accept ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: mitz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-30 11:35 PDT by mitz
Modified: 2014-10-30 11:49 PDT (History)
1 user (show)

See Also:

Attachments
Include NSErrorClientCertificateChainKey when encoding error user info (3.94 KB, patch)
2014-10-30 11:38 PDT, mitz 		ap: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2014-10-30 11:35:44 PDT 
When trying to authenticate to a website using a client certificate, if the server rejects the certificate, Safari shows an error sheet saying “The website “…” did not accept the certificate “unknown””. Instead of “unknown” it is supposed to name the certificate that was used. It’s not working because the error object is missing the NSErrorClientCertificateChainKey key in its userInfo dictionary.

Patch forthcoming.
Comment 1 mitz 2014-10-30 11:38:24 PDT 
Created attachment 240684 [details]
Include NSErrorClientCertificateChainKey when encoding error user info
Comment 2 Alexey Proskuryakov 2014-10-30 11:44:17 PDT 
Comment on attachment 240684 [details]
Include NSErrorClientCertificateChainKey when encoding error user info

View in context: https://bugs.webkit.org/attachment.cgi?id=240684&action=review

> Source/WebKit2/Shared/mac/WebCoreArgumentCodersMac.mm:203
> +        ASSERT(^{

Fun times.
Comment 3 mitz 2014-10-30 11:49:01 PDT 
Fixed in <http://trac.webkit.org/r175374>.