Bug 133617 - [Mac] Client-certificate authentication isn’t working when using the modern API
Summary: [Mac] Client-certificate authentication isn’t working when using the modern API
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: InRadar
Depends on:
Blocks:
 
Reported: 2014-06-08 12:18 PDT by mitz
Modified: 2014-06-08 12:30 PDT (History)
1 user (show)

See Also:

Attachments
Use OS X API for key coding (4.53 KB, patch)
2014-06-08 12:21 PDT, mitz 		sam: 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-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.
Comment 1 mitz 2014-06-08 12:21:58 PDT 
Created attachment 232684 [details]
Use OS X API for key coding
Comment 2 mitz 2014-06-08 12:30:55 PDT 
Fixed in <http://trac.webkit.org/r169682>