Any word on whether or not this bug, from iOS 3, has been fixed by now? rdar://problem/7492560 We have a self-signed server cert that I deal with by handling NSURLAuthenticationMethodServerTrust challenges in -connect:willSendRequestForAuthenticationChallenge:. But now I need to ALSO support client-side SSL, and the AdvancedURLConnections sample code has this in the Readme:
It seems that it's not currently possible to respond to both a NSURLAuthenticationMethodServerTrust challenge and a NSURLAuthenticationMethodClientCertificate challenge. That is, if an HTTPS server has a non-trusted server identity and requires that you provide a client identity, things don't work as expected (you get the NSURLAuthenticationMethodServerTrust challenge but the connection fails before you get the NSURLAuthenticationMethodClientCertificate challenge). We're still investigating this issue <rdar://problem/7492560>. In the meantime, the workaround is to install the server's root certificate globally (but beware of the simulator problems described earlier).
Am I going to run into issues? -- Rick Mann rmann@latencyzero.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com