Hi All,

In an API call which goes from APIGW to WM.io is it possible to implement basic auth on the APIGW only?
Currently when calling .io from APIGW we have a routing rule set up to call .io with a generic account so it has access.
With this set up users we give access to APIGW via Oauth will never have access to .io or Cloud pages, however it doesn't seem possible to use this set up for basic auth.

What is the best practice for setting up basic auth on APIGW > .io integration workflow?

Thank you!

hi Garry,

If we are planning to invoke the workflows from API GW then we need to route the request using the routing policy available in API GW.

1. currently on the workflow side we provide option  where the webhook endpoints of workflow can be invoke using
   1. basic credentials
   2. Authorization key
   3. None.
2. Now we have to decide from the above options.
3. With my past experience  client has configure the basic creds in the API GW routing policy  and from their the request is routed successfully to the .io workflows.
4. Now when when we talk about the crdentials we can either pass it explicitly in the routing policy or we can use the incoming basic cred and then same can be forwared to the workflow invocation.
5. for the routing policy please refer the below link

        https://docs.webmethods.io/saas/webmethods-api-gateway/11.1.0/getting_started/chapter14a/#co-routing_policies

Regards

Vikash Sharma