![]() You can verify the contents of the key anycodings_java store using the Java keytool utility anycodings_java with the following command: keytool -v -list -keystore mykeystore.p12 -storetype pkcs12įinally if you need to you can convert anycodings_java this to a JKS key store by importing the anycodings_java key store created above into a new key anycodings_java store: keytool -importkeystore -srckeystore mykeystore.p12 -destkeystore clientcert.jks -srcstoretype pkcs12 -deststoretype JKSĠ T20:28:39+00:00 T20:28:39+00:00 Answer Link NOTE that the name provided in the anycodings_java second command is the alias of your key anycodings_java in the new key store. However, keep anycodings_java in mind that depending on who you get anycodings_java the certificate from (intermediate CA, anycodings_java root CA involved or not) or how the pfx anycodings_java is created/exported, sometimes they anycodings_java could be missing the certificate chain. ![]() anycodings_java After Import, You would have a anycodings_java certificate of PrivateKeyEntry type, but anycodings_java with a chain of length of 1. anycodings_java The easier option in my mind is to anycodings_java import and export the pfx file in anycodings_java IE(choosing the option of Including all anycodings_java the certificates in the chain). The anycodings_java import and export process of anycodings_java certificates in IE should be very easy anycodings_java and well documented elsewhere. ![]() Once exported, import the keystore as anycodings_java Justin pointed above. Now, you would anycodings_java have a keystore with certificate of type anycodings_java PrivateKeyEntry and with a certificate anycodings_java chain length of more than 1.Ĭertain. ![]()
0 Comments
Leave a Reply. |