Timeline for Propagating certificates stored in a CNG Key Store Provider
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2018 at 9:43 | comment | added | Frank | Thanks for the comment. This helps me a lot as I know now that the propagation works as expected and the problem lies somewhere else. I have found some strange entries in the windows event log and think this is the path I will follow for the next stage of research of the problem. | |
| Apr 26, 2018 at 15:09 | comment | added | Fabiano Pereira | Frank, I was not able to post a comment to your other question due to lack of enough points.You said that certutil was able to make a digital signature using your KSP, this indicates that your KSP is properly configured and active, otherwise NCryptSignHashFn would not have been called. The authentication in the browser may be failing due to other factors. Is the web server properly configured to accept the certificate chain that was used to issue your certificate? | |
| Apr 26, 2018 at 15:03 | vote | accept | Fabiano Pereira | ||
| Apr 25, 2018 at 7:30 | comment | added | Frank | Thanks for the useful answer. Using this I was able to get my certificate displayed in the browser when a client certificate is required. However, when I select the certificate and klick "OK" my KSP is not called. Do you have any idea what this could be? Perhaps the registration of the KSP? Answers can be left in this SO-question | |
| Feb 14, 2017 at 13:01 | history | answered | Fabiano Pereira | CC BY-SA 3.0 |