SSL client certificate needs special contents? -


I have a server with customers having SSL certificates and SLC certificates, all are signed by the same CA, and the CA server And the client was trusted as a root authorization.

Although I have tried (no iPhone, Chrome, Explorer) clients will not send any client certificates when the server requests it, even if they all confirm that the server certificate is ok is not.

When I look at the certificate certificate in the certificate / profile / store, they all claim that it is verified and legal, and all the certificates verified properly by using openssl etc. We do.

An SSL client certificate requires a specific name or other description, so when do the customer browsers know its usage? Like how to specify the correct domain name on a server certificate certificate?

The server is an apache2.2 server, but I do not think the server is a problem at the end

  1. Customer certificates should have the appropriate key usage and extended key usage extensions set. I certainly do not know what is "justified" in your case, but the number of variants in main use is very small and you can check yourself for different values.
  2. You certainly have not forgotten about the private key that should be accessible on the client side, are you?

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -