title: Sending an HTTP request with client certificates in Chrome
body: <p>I have an API on Azure that is protected with <a href="https://en.wikipedia.org/wiki/Mutual_authentication" rel="nofollow noreferrer">mutual authentication</a>. The server certificate is internally handled by Azure:</p>
  
  <p><a href="https://i.stack.imgur.com/MvSgT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MvSgT.png" alt="Server Certificate"></a></p>
  
  <p>I've created a self signed certificate and added it to my local computer's list of <em>Trusted Root Certification Authorities</em> as well as my <em>Personal</em> certificates:</p>
  
  <p><a href="https://i.stack.imgur.com/tlVST.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tlVST.png" alt="Client Certificate"></a></p>
  
  <p>When attempting to hit the API through Chrome (specifically the Chrome App Postman), I'm getting a 403 indicating my request didn't have a certificate associated with it.</p>
  
  <ol>
  <li>Do I have a misunderstanding of how this should work?</li>
  <li>It's possible I've created the client certificate incorrectly. Everything I read online point to using OpenSSL to create these, however I had some issues getting it to run on a Windows machine and went through a variety of other tools: <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/aa386968(v=vs.85).aspx" rel="nofollow noreferrer">MakeCert</a>, PowerShell's <a href="https://technet.microsoft.com/en-us/library/hh848633(v=wps.630).aspx" rel="nofollow noreferrer">New-SelfSignedCertificate</a>, and <a href="http://www.selfsignedcertificate.com/" rel="nofollow noreferrer">Self-Signed Certificate Generator</a>. All seem to create certificates, but I have no real way of knowing if I created them correctly.</li>
  <li>If the certificate was created correctly, how do I get Chrome to submit the certificate with the request? Shouldn't it just automatically pick up the cert when I add it to the store?</li>
  </ol>