Bug 133617

Summary: [Mac] Client-certificate authentication isn’t working when using the modern API
Product: WebKit Reporter: mitz
Component: WebKit2Assignee: mitz
Status: RESOLVED FIXED    
Severity: Normal CC: ap
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Use OS X API for key coding sam: review+

mitz
Reported 2014-06-08 12:18:17 PDT
<rdar://problem/17208234> For client-certificate authentication, clients respond to an authentication challenge with an NSURLCredential initialized with an identity and (optionally) a certificate chain. On Mac, we currently fail to properly encode such credentials when sending them to the Network process, so authentication always fails. The fix for bug 133527 ended up being iOS-specific, but we can do something similar for Mac (using alternative Security APIs). Patch forthcoming.
Attachments
Use OS X API for key coding (4.53 KB, patch)
2014-06-08 12:21 PDT, mitz 		sam: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
mitz
Comment 1 2014-06-08 12:21:58 PDT
Created attachment 232684 [details] Use OS X API for key coding
mitz
Comment 2 2014-06-08 12:30:55 PDT
Fixed in <http://trac.webkit.org/r169682>
Note You need to log in before you can comment on or make changes to this bug.