0

I have an application that we have set up to use client certificate authentication in test and when I access it from my development machine running windows 10 it prompts me to select the certificate. Then having done so it takes me to a 403 forbidden page which on looking in the iis logs is a 403.7.

My development machine is running windows 10 and I get the same error browsing with firefox or IE.

If I install my client certificate on a different machine it works.

The client certificate has a primary key and all stages are trusted, and the trusted root ca is in my trusted roots.

The SSL handshake is completing successfully its rejecting at the certificate end.

Additionally trying to access the production environment has the same behaviour when done from my windows 10 machine, and works from other machines.

Thanks for the help

Ben Whyall
  • 268
  • 3
  • 17
  • You are saying the same client certificate installed on a different computer works fine ? but when using localhost,it does not work fine.Am I correct ? – Rohith Jun 20 '17 at 13:47
  • The site I am trying to connect to is on a server A. From my client machine B the certificate doesn't work when I connect to A, from client machine C it does. – Ben Whyall Jun 20 '17 at 15:09

1 Answers1

0

As you are experiencing issue with local machine only,this probably is because of clientcertnegotiation setting. Look at second answer of this question - using netsh to enable clientcertnegotiation

Rohith
  • 5,527
  • 3
  • 27
  • 31