Two IFS Cloud environments (for example, IFS Cloud and a separate PSO deployment) need to trust each other's certificates for secure integration, but there's no reconfigure-based certificate import like there was on IFS10 — how is a third-party certificate actually applied to the Cloud keystore for this kind of integration/communication (as opposed to document-signing)?

All FAQ questions / Integrations and APIs

Answer

Download the certificate from the other system, then add it under the ifscore certificates section of your Cloud installation's values file, nested under the specific deployment it needs to be trusted by (for example, under an ifsapp-connect entry, keyed by a name identifying its purpose). Apply the updated values file by running the ifsinstaller with the mtinstaller action, then restart the relevant deployment's pods so they pick up the newly mounted certificate — for IFS Connect specifically, that means scaling the ifsapp-connect deployment down to zero replicas and back up. This values-file-plus-restart pattern is the Cloud-native replacement for the old IFS10 reconfigure-based certificate import.

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