RE: Microgateway

Not applicable

Hi All,

I am learning how I can leverage Micro-gateway on on-premis infrastructure, And I am able to spin-up a POC, and able to send request and get response back.

However what I don't get is, if I make a HTTP request to Apigee endpoint e.g.

http://myorg-eval-test.apigee.net/hello/echo, it also executes and I get back the same request/response,

isn't meant to pass only through Micro-gateway - Node.js app - ONLY, rather than the Apigee, Edge endpoint as well ? or there is a way of restricting the request to only allow from Micro ?

Thanks

1 3 221
3 REPLIES 3

You may refer:https://docs.apigee.com/api-platform/microgateway/2.5.x/setting-and-configuring-edge-microgateway.html

@Seshadri Ramanujam

Thanks for suggesting the document. However, I have gone through it and read it a few times before attempting setting up Edge Mictogateway. And it works as advertised, from beginning to the end.

On the other hand, what I don't get is why the request via http://myorg-eval-test.apigee.net/hello/echo, it's still working. I assumed that the access would be ristricted to the micro-gateway instance and request from Edge would be restricted. Please let me know if my thinking is correct or If I have missed a critical information in the document let me know.

Thanks

Iam unable to view your proxy. If you could post the trace session report we can make out something from that.

The microgateway always works hand in hand with Edge when it comes to issuing tokens etc. However as long as it is prefixed with edgemicro the run time traffic of the respective proxies will be only through microgateways