Good day! I wanted to implement authorization on the site through the ESIA using OpenConnect help. In turn, created a certificate using OPENSLL and sent. I confirmed the certificate. There are private keys in the test keys. And the certificate I created * .p12 does not have a file with private keys. Question: How can I get this private key? In order to sign a request to send.

  • If you are given an exhaustive answer, mark it as correct (a daw opposite the selected answer). - Nicolas Chabanovsky ♦

3 answers 3

You should have created the private key when you created the certificate using OpenSSL. Look for it in your files. If you delete it - congratulations, you do everything again.

    Well, Pavel Mayorov answered correctly. I will add that it will be necessary to submit an application for "changing the connection parameters to the test / industrial" ESIA. Request form here: http://esia.pro/blanki_zayavok will send the current version according to the regulations. Just indicate that you need it for reconnection and the type of organization: state / commerce.

      Thanks for the comments! The certificate * .p12 includes the private key. Using dotnet, you can sign the request X509Certificate2 cert = new X509Certificate2 (string fileName, string password, X509KeyStorageFlags keyStorageFlags).