![]() ![]() Once full chain is decided and cert files are copied made ready Import Certs to gatewayĪlways start importing from root to Gateway. Here is snapshot of how it looks like:Īlso, in order to get chained cert you can also run openssl pkcs7 -inform DER -text -print_certs -in /tmp/cert/.p7c ( you can get the certificate and examine in keystore explorer and see if you can get the full chain) If you don't see the full chain then just go ahead and open and check each and every chained cert's if you find "Authority Information Access" having a link to download further chain.Download the certificate and then open it in the Keystore Explorer and check if you see the full chained certificate until you reach the AKI of "gateway.pem" => Extensions 36 Import Export Compliance jobs available in Seattle, WA on.After opening that file you should be able to see "Authority Information Access" => extension value and you should be able to get a link to download a certificate For Ex: "URI: ".Open up gateway.pem or the file you copied that "CSR reply" in Keystore Explorer.Now, if you see any error after running above command for "chain certificate not found or something can't relate to chained certificate" then you need to generate to get the chained certificate as mentioned below. This is importing a CSR reply to allow for existing root certificate to be chained to the intermediate and root certificates. ![]() ![]() This is NOT importing a new SSL certificate to replace what is currently in the key store. Keytool -import -trustcacerts -alias gateway -file gateway.pem -keystore gateway.jks ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |