Darius,
If you don't want to provide a System.Net trace, you can put together a simple app to prove the client side certs are working.
Here would be the cs code behind a simple page:
try
{
HttpClientHandler aHandler = new HttpClientHandler();
aHandler.ClientCertificateOptions = ClientCertificateOption.Automatic;
HttpClient aClient = new HttpClient(aHandler);
HttpResponseMessage aResp = await aClient.GetAsync("https://jsanders4.northamerica.corp.microsoft.com/");
txtBlock.Text = aResp.StatusCode.ToString();
}
catch (Exception theEx)
{
txtBlock.Text = theEx.Message;
}
and the entries you should have in your manifest:
<Capabilities>
<Capability Name="sharedUserCertificates" />
<Capability Name="enterpriseAuthentication" />
<Capability Name="privateNetworkClientServer" />
<Capability Name="internetClient" />
</Capabilities>
<Extensions>
<Extension Category="windows.certificates">
<Certificates>
<SelectionCriteria HardwareOnly="false" AutoSelect="true"/>
</Certificates>
</Extension>
</Extensions>
-Jeff
Jeff Sanders (MSFT)
Unfortunately I'm not able to get it working. I followed the same steps but still getting a 403 error. I'm first installing the certificate using "ImportPfxDataAsync" function and I can see the certificate file being created in my local store ("My") [the
name of the file is the certificate thumbprint and for some reason the extension of that file is "sys"].
This is the code for installing the certificate:
Task t = Task.Factory.StartNew(() => CertificateEnrollmentManager.ImportPfxDataAsync(certificateData, "test", ExportOption.Exportable, KeyProtectionLevel.NoConsent, InstallOptions.None,
"My Test Certificate").AsTask());
t.Wait();
and this is the code for sending the request:
private async Task LetTheFunBegin()
{
try
{
HttpClientHandler aHandler = new HttpClientHandler();
aHandler.ClientCertificateOptions = ClientCertificateOption.Automatic;
HttpClient aClient = new HttpClient(aHandler);
HttpResponseMessage aResp = await aClient.GetAsync("https://myuri.com");
string a = await aResp.Content.ReadAsStringAsync();
var abc = aResp.StatusCode.ToString();
}
catch (Exception theEx)
{
var def = theEx.Message;
}
}
The manifest file looks like following:
<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/2010/manifest">
....
<Capabilities>
<Capability Name="sharedUserCertificates" />
<Capability Name="enterpriseAuthentication" />
<Capability Name="privateNetworkClientServer" />
<Capability Name="internetClient" />
</Capabilities>
<Extensions>
<Extension Category="windows.certificates">
<Certificates>
<SelectionCriteria HardwareOnly="false" AutoSelect="true"/>
</Certificates>
</Extension>
</Extensions>
</Package>
However I am always getting 403 error. It seems the certificate is not being picked up at all.
Any inputs will be highly appreciated.
Thanks
Gaurav
Using Client Side Certificates in Windows Metro
