Please vote if this is an important scenario for you. If the lack of this feature is is blocking your adoption of the C++ REST SDK, please comment below.
Note: We cannot guarantee that this feature will be supported in upcoming releases. However by voting we will be able to better understand our customer's need and help us in prioritizing future work.
Comments: Hi rathi8579, We haven't do any work on adding high level API support for client side certificates in Casablanca. We've had customers successfully do so using our feature that allows access to the underlying native handle on the platform for http request. Take a look at http_client_config::set_nativehandle_options. It allows you to specify a callback to change any settings. For Windows store application we build on [IXMLHttpRequest2](http://msdn.microsoft.com/en-us/library/windows/desktop/hh831151(v=vs.85).aspx). For IXMLHttpRequest2 it looks you can a prompt pop up for credentials and certificates using [XHR_PROP_NO_CRED_PROMPT](http://msdn.microsoft.com/en-us/library/windows/desktop/hh831167(v=vs.85).aspx) option. We turn it off by default since Casablanca is a library only solution. This might of use as well, here is an [msdn thread](http://social.msdn.microsoft.com/Forums/windowsapps/en-US/d9ca6629-521e-4949-a637-de2f68e52065/need-help-on-choosing-a-networking-api?forum=winappswithnativecode) with a user about client certs and they seem to be successful at the bottom. In regards to the error, we are aware of the bad error message here it is already fixed for out next release :). To get more information you can catch the exception thrown, of type http_exception, and then take a look at the underlying std::error_code causing the problem with the error_code() method. Thanks, Steve
Note: We cannot guarantee that this feature will be supported in upcoming releases. However by voting we will be able to better understand our customer's need and help us in prioritizing future work.
Comments: Hi rathi8579, We haven't do any work on adding high level API support for client side certificates in Casablanca. We've had customers successfully do so using our feature that allows access to the underlying native handle on the platform for http request. Take a look at http_client_config::set_nativehandle_options. It allows you to specify a callback to change any settings. For Windows store application we build on [IXMLHttpRequest2](http://msdn.microsoft.com/en-us/library/windows/desktop/hh831151(v=vs.85).aspx). For IXMLHttpRequest2 it looks you can a prompt pop up for credentials and certificates using [XHR_PROP_NO_CRED_PROMPT](http://msdn.microsoft.com/en-us/library/windows/desktop/hh831167(v=vs.85).aspx) option. We turn it off by default since Casablanca is a library only solution. This might of use as well, here is an [msdn thread](http://social.msdn.microsoft.com/Forums/windowsapps/en-US/d9ca6629-521e-4949-a637-de2f68e52065/need-help-on-choosing-a-networking-api?forum=winappswithnativecode) with a user about client certs and they seem to be successful at the bottom. In regards to the error, we are aware of the bad error message here it is already fixed for out next release :). To get more information you can catch the exception thrown, of type http_exception, and then take a look at the underlying std::error_code causing the problem with the error_code() method. Thanks, Steve