IFS Connect Transport Connectors (HTTP/REST/Mail senders) need to trust a certificate for an SSL-secured third-party endpoint, but the standard on-prem documentation for importing it into a Java truststore via keytool assumes direct access to the application server/Docker container filesystem, which isn't available on Cloud or BuildPlace-hosted environments — how is this actually done in Cloud?

All FAQ questions / Integrations and APIs

Answer

From around IFS Cloud 22.2.4 onward, there's a built-in option directly on the Routing Address screen to import a certificate — this avoids needing keytool/truststore filesystem access entirely, which isn't available in managed Cloud environments anyway. Check the Routing Address configuration for that import-certificate option before assuming you need container-level access to trust a third-party certificate for a Transport Connector.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions