This is definitely an Entrust product question. Usually, you will not
see the certificate extensions when you're approving a CSR (unless the
PKI builders chose to make it visible to you). Configuring the CA to
tweak the key-usage bits requires going into some configuration mode
(perhaps through
Vivek Kumar wrote:
> Could anyone please tell me how to change the extension of the server
> cert to include "Key encipherment" for KeyUsage? When creating the
> server cert I did not see any options to modify the attribute..
> We have setup the CA using Entrust and uisng IIS 6.0 as the web-server
I am facing the same issue, client authentication working with IE but not with NSS/FF/Mozilla :
"Could not establish an encrypted connection because certificate presented by is invalid or corrupted. Error code: 8102"
Could anyone please tell me how to change the extension of the server cert to
3 matches
Mail list logo