Clients Trust the eFTL Service
When TLS security is enabled, client applications connect using the WSS protocol, and must trust the certificate of the FTL server (or of the eFTL service).
Certificate to Trust
New or updated client applications connect through the FTL server port, and must trust the FTL server's certificate.
In contrast, legacy eFTL client applications connect directly to the listen port of the eFTL service, and must trust the eFTL service's certificate.
Register Certificates
The Java and Objective C APIs include a method to register the certificates that the application trusts.
In .NET, install the certificate into the Microsoft certificate store before starting an eFTL client program. For details, see Microsoft documentation.
When running JavaScript applications in a Node.js environment, the application must register the certificates that the application trusts. (However, the JavaScript method that registers certificates applies only when running in a Node.js environment. It is not effective when running in a browser.)
When running JavaScript applications in a browser, the browser is responsible for trusting certificates. Unless the browser already trusts the certificate, it will not connect. To register trust, users must complete the task Accepting a Self-Signed Certificate.
- Accepting a Self-Signed Certificate
To instruct your browser to accept the FTL server’s certificate or the eFTL service's certificate, complete this task.