In App 10, we can use the APIs in compatibility application type and access them through the int gateway. However, it seems this option is not available in the cloud. Is there any possibility to expose all main APIs through the int gateway?
Best regards,
APP10
Cloud
Best answer by Rifki Razick
Hi,
The main reason to have the “Include in Application Compatibility Type” feature in IFSAPPS 10 was to make it possible to use http basic authentication on the “int” context for APIs that were available on the “main” context. However IFS Cloud no longer supports/recommends http basic authentication due to security reasons. This means you can directly use the APIs from the main context using OAuth negating the need for “Include in Application Compatibility Type” in IFS Cloud.
The main reason to have the “Include in Application Compatibility Type” feature in IFSAPPS 10 was to make it possible to use http basic authentication on the “int” context for APIs that were available on the “main” context. However IFS Cloud no longer supports/recommends http basic authentication due to security reasons. This means you can directly use the APIs from the main context using OAuth negating the need for “Include in Application Compatibility Type” in IFS Cloud.
You can do this by setting the ifsappproxy.basicAuthEnabled to true in the ifscloud-values.yaml file. However, as Rifki has mentioned above, and the documentation itself has emphasized, this compromises system security, hence highly not recommended.
Does this mean, using Main would compromise security? We are facing some issues when trying to setup a simple integration and for us, Int cluster is not working. Replacing the Int with Main is allowing us to access the API.
Does this mean, using Main would compromise security? We are facing some issues when trying to setup a simple integration and for us, Int cluster is not working. Replacing the Int with Main is allowing us to access the API.
@Charith Epitawatta , if we configure ifsappproxy.basicAuthEnable, will it enable the button for the compatibility option?
I haven’t tried this myself, but it will not enable the button you are referring to which is available in IFSAPP10. This change is done in proxy level. Therefore, once the change is done, if you describe the ifsapp-proxy container, you would see the environment variable “BASIC_AUTH” is set to enabled.
kubectl describe pod ifsapp-proxy-xxxxxxxx-xxxx -n <namespace>
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.