Quick Start – When Certificates are required for authentication
Quick Start – When Certificates are required for authentication
Follow these steps if the FTPS server needs to authenticate your client certificate and/or if you need to authenticate the trading partner's certificate.
Follow these steps if your trading partner requires your public SSL certificate for authenticating your client:
Create a Certificate in the
Default Private Keys
key store.
If your trading partner requires that your certificate is signed by a third party (not self-signed), then follow the steps below:
Generate a Certificate Signing Request (CSR) and send it to an Issuer (your trading partner or a
Certificate Authority (CA)
).
After you receive the signed certificate (reply) from the Issuer, then import the reply into your
Default Private Keys
key store.
You must also import the certificate of the Issuer that signed your certificate into the Key Store.
If this is a certificate chain, where the certificate that signed your certificate was signed by another certificate and so on, then all certificates in the chain must be added to your Key Store.
If your certificate was not signed by a third party (self-signed), then Export your Certificate and send it to your trading partner.
Follow these steps if you want to use your trading partner's public certificate for authenticating their server:
If your trading partner's certificate was not signed by a third party (self-signed), then request the public certificate from your trading partner.
Import their public certificate into the Default Trusted Certificates Key Store.
If this is a certificate chain, where the certificate that signed your certificate was signed by another certificate and so on, then all certificates in the chain must be added to your Key Store.