Connecting Securely to On-Premise Backends from MobileFirst on IBM Bluemix containers
Note: This procedure is no longer applicable. Use the VPN service for MobileFirst Platform Foundation 7.1 on Containers. For instructions for MobileFirst server running on Liberty buildpacks and Mobile Foundation Bluemix service (which also runs on Liberty buildpack), pl refer to this blog post.
With the IBM MobileFirst Platform Foundation 7.1 release there is an option to run the MobileFirst Platform Foundation Server on the IBM Container service on IBM Bluemix. This option enables you to build docker images of your IBM MobileFirst Foundation runtimes and then run them on the IBM Container Service. The advantage here is that you do not need to roll your own infrastructure. In this blog post we will deal with the problem of connectivity with on-premise backends. This is a common use case for an enterprise to have its MFP adapters connect to backends that are hosted on-premise. We will use the Mutual Authentication feature provided by the Secure Gateway service to ensure that the traffic between the Secure Gateway client which runs on-premise and the Secure Gateway cloud endpoint is encrypted and thus safe from man in the middle attacks.
The ibm-mfpf-container-188.8.131.52.eval.zip archive file should have been downloaded and extracted into a directory say ibm-mfpf-container-184.108.40.206.eval. Users should also be familiar with deploying their MobileFirst Platform Foundation projects on the IBM container service and have all the pre-requisites installed on the system where they are going to run the secure gateway client. If they are not, then they should read the article linked below
Connecting to On-Premise
In order to support communication over TLS from an adapter to Secure Gateway we would need to use a TLS proxy. In this post we will use stunnel an opensource TLS proxy to connect to the public endpoint exposed by the Secure Gateway service on IBM Bluemix. We will install this proxy inside the docker container and it will listen for unencrypted calls at a particular local port. The EIS connectivity driver can then make calls to this local port on the docker container which are then transmitted by stunnel over TLS to the secure gateway public endpoint. This is shown in the figure below
Steps to connect to On premise with Mutual Auth
- Login to the IBM Bluemix PAAS Platform.
- Open the Bluemix Dashboard and click on the Use Services or APIs button.
- Go to the integration section and select secure gateway.
- Let the App be left unbound and select the standard plan.
- Click the use button and the secure gateway dashboard is opened.
- Click on the ‘Add Gateway’ button. This will bring up the Add Gateway screen.
- Enter a name for the gateway say ‘testGateway’. Leave the enforce security token on client checkbox unchecked.
- Click on Connect it.
- You will be displayed a docker run command like docker run -it ibmcom/secure-gateway-client nPtTLWKrrKC_prod_ng. Copy and paste the command exactly as its shown to you and run it on the on premise system.
- This will result in a docker image being downloaded from the repository and its then run. Wait until you get the following message:
The Secure Gateway tunnel is connected
- Click on “Add Destinations” and you are shown a Create Destinations section. Enter any name as the destination name . Enter the IP address of the on premise system you want to connect to along with the port. Choose the protocol to be TLS: Mutual Auth. Eg of IP address and port can be 192.168.1.3 and 3306 where the IP address is the IP address in the on-premise network and port is the port on which the EIS is listening.
- Click the + button to add the destination.
- Click on the Info icon on the destination tile and you get the cloud host and port which you need to save somewhere for future use.
- Click on the settings button, on the top right corner of the destination tile, and select download keys to download the keys for mutual authentication. These keys need to be extracted to a directory called certs. We will use them later.
- Change the dockerfile present in the ibm-mfpf-container-220.127.116.11.eval/mfpf-server directory to install a tunneling proxy called stunnel. We will need this tunnel to connect to the secure gateway over TLS. Stunnel will then expose an unsecured host and port locally which we will then use to connect to the onpremise Enterprise Information System like database ldap etc. Use the docker file attached below to replace the one in your mfpf-server directory.
- Create an ibm-mfpf-container-18.104.22.168.eval/mfpf-server /stunnel/certificates directory and drop the keys and certificates downloaded in step 14 inside this directory.
- Create an stunnel.conf file inside the same directory as #17. This file should have the following contents
- The cert and key values correspond to the path of the client certs that were generated by Secure Gateway in step 14 and will be of the format shown above i.e. ends with _cert.pem and _key.pem.
- The CApath points to the directory containing the server certificates namely secureGatewayCert.pem, DigiCertTrustedRoot.pem and DigiCertCA2.pem i.e. /opt/ibm/certs.
- The connect property should have the value that you got in step 13, i.e. the cloud host and port eg cap-sg-prd-1.integration.ibmcloud.com:15391.
- The accept property should have the unsecured host and port name to which your adapter or any other code running in the docker container will connect to. The stunnel proxy will then listen at that port for unsecured requests from the MobileFirst Platform Foundation server. The client property should be yes.
- Modify the mfp-init file in ibm-mfpf-container-22.214.171.124.eval/mfpf-server /server/bin to contain the command to start the secure tunnel i.e. service stunnel4 start.
- Ensure that in the MobileFirst adapter configuration or any other artifact that you are using to connect to the on premise EIS, you use the hostname and port specified in accept property in step 17 i.e. 127.0.0.1 and 4409.
You can now follow the steps to build, deploy and run your container on Bluemix as mentioned in