Hi, I want to consume my Apigee API Proxy from an AppScript application using the
Solved! Go to Solution.
I am not an expert on Google AppScript but it appears that UrlFetchApp does not support mutual TLS directly. [ see this and this ]. Therefore you cannot authenticate your client with mutual TLS, if you are using UrlFetchApp.
You may want to "work around" the problem by relaxing the requirement to use 2-way TLS, and use some other form of client authentication here. For example,
I am not an expert on Google AppScript but it appears that UrlFetchApp does not support mutual TLS directly. [ see this and this ]. Therefore you cannot authenticate your client with mutual TLS, if you are using UrlFetchApp.
You may want to "work around" the problem by relaxing the requirement to use 2-way TLS, and use some other form of client authentication here. For example,
Thank you for your answer, we didn't want to make a proxy and ask for infrastructure resources just to add a certificate to our requests but it appears to be our only option. JWT approach was not approved by my team
You could also use a pre-built proxy, that requires only configuration. For example I thnk Envoy Proxy can accept inbound connections over -way TLS and then create outbound connections (to an upstream) via 2-way TLS. [ link ]
Envoy may be lightweight enough to run as a local proxy, on the machine that runs AppsScript. Or you could use a shared Envoy in a managed instance group.