Accessing myFileGateway 2.0 using Sterling Secure Proxy

You can access myFileGateway 2.0, either deployed on ASI server with base port or on HTTP Server adapter running on ASI or AC pods, using Sterling Secure Proxy.

Note: It is assumed that Sterling Secure Proxy is running as a container within the same Kubernetes cluster as Sterling B2B Integrator.

You can follow the standard process of creating the adapters on Sterling Secure Proxy, but you must take extra care when you create HTTP Netmap Nodes for myFileGateway 2.0 adapter. Depending on where you deploy myFileGateway 2.0 in Sterling B2B Integrator, you must provide either ASI or AC front end service IP address or Name and the Port number opened on that service, which directs to the correct internal destination port as a part of Outbound nodes.

For more information, see IBM® Sterling Secure Proxy V6.0.2 documentation.

Annotating myFileGateway 2.0 routes (v6.1.0.3 and later versions)

When installing Sterling Secure Proxy outside of the Red Hat OpenShift cluster, where Sterling B2B Integrator is running, Sterling Secure Proxy must forward the incoming requests to the necessary routes created for myFileGateway 2.0. In this case, you must disable the cookies generated by the OpenShift routes, and suitably annotate them.

You can annotate the routes using the following attributes:	true	        source
You can use the following commands to annotate the routes:

oc annotate route <name of route> --overwrite
oc annotate route <name of route> --overwrite

Alternatively, you can use the OpenShift console UI to modify the annotations. Go to Networking > Routes. Open the routes created to access myFileGateway 2.0 and modify the annotations, as required.

Important: The above changes are applicable only when myFileGateway 2.0 supports Single Sign On (SSO) using Sterling Secure Proxy.