I’ve lately obtained an S/MIME certificates from a CA to make use of with Thunderbird on a Linux system.
I used the next command in CLI : openssl pkcs12 -export -in certificates.crt -inkey private_key.pem -certfile cert_CA.crt -out my-cert.pfx
I then put in my-cert.pfx in Thunderbird and this works simply high-quality.
I proceeded to additionally import the identical .pfx file onto my iPhone bu this ends in an error when requested for certificates password. Coming into the established certificates password does not work as per directions and it seems prefer it’s not recognised, despite the fact that I’m positive I’ve used the proper password ?!?
I’m not positive however I believe that by default the openssl command could have encrypted the output .pfx certificates file with a special encryption to that which iOS expects by default, and so the identical certificates password shouldn’t be recognised accurately.
Any strategies as to what could also be the issue and find out how to generate a .pfx file utilizing openssl in CLI in order that iOS will settle for the set certificates password ?
I had used the Home windows Certificates Supervisor Instrument to export my non-public key and this required setting a certificates password (no different choice was obtainable).
Thanks upfront for any strategies on find out how to accurately generate and import the .pfx certificates file to work on my iOS units…
Adopted the overall directions on importing a .pfx certificates into iOS and the beforehand set certificates password was not recognised/accepted despite the fact that it was appropriate.
