You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have one specific instance of an implementation that will not add the chain certificates to the PFX such that they can be exported. Noticed in v 1.3.1 and repeated on v 1.5.0. This issue is only occurring on a single client at the moment.
In our implementation, after we export the PFX file we make three calls to openssl in order to extract the client cert, the chain cert, and the key. The key and client cert are created properly, but the chain is not. We then import these three files into our server app (FileMaker Server).
To date this has only happened on 1 out of about 130 instances. I can deliver the entire State folder if it would be helpful for inspection.
The text was updated successfully, but these errors were encountered:
I think it would be helpful to get the associated order (-Verbose will probably tell the filename).
Also the PEM file from your ACME server and the File containing the servicedirectory (part of state). Make sure to not include AccountKey and CertificateKey. Write me an email, if you don't want to expose it here.
Also setting $VerbosePreference = 'Continue' might print out the whole script, so we can see everything that happens along the way.
I have one specific instance of an implementation that will not add the chain certificates to the PFX such that they can be exported. Noticed in v 1.3.1 and repeated on v 1.5.0. This issue is only occurring on a single client at the moment.
In our implementation, after we export the PFX file we make three calls to openssl in order to extract the client cert, the chain cert, and the key. The key and client cert are created properly, but the chain is not. We then import these three files into our server app (FileMaker Server).
To date this has only happened on 1 out of about 130 instances. I can deliver the entire State folder if it would be helpful for inspection.
The text was updated successfully, but these errors were encountered: