You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have an instance of Microgateway correctly connected with a Manager
following the instructions of IBM, but when we make petitions from Api
Manager, these not are arrived to microgateway.
WE have a microgateway instance with env.yaml and id_rsa.pub.
We have a Manager with a catalog pointed to microgateway with env and
id_rsa.
We have not collectives.
We know the manager and microgateway are correctly connected because we
can see that in logs.
NOw, whe we make an simple API from Developer Toolkit or Manager, for
example, we have not response (404) and in Microgateway logs have not
anything, so our petitions are not correctly connected.
Please, could you help us to connect correctly Manager->Microgateway??
The text was updated successfully, but these errors were encountered:
The Microgateway is the runtime independent from the API manager. When you configure the Microgateway, there is a setting for the custom Gateway URL that maps to the actual gateway endpoint.
we have an instance of Microgateway correctly connected with a Manager
following the instructions of IBM, but when we make petitions from Api
Manager, these not are arrived to microgateway.
WE have a microgateway instance with env.yaml and id_rsa.pub.
We have a Manager with a catalog pointed to microgateway with env and
id_rsa.
We have not collectives.
We know the manager and microgateway are correctly connected because we
can see that in logs.
NOw, whe we make an simple API from Developer Toolkit or Manager, for
example, we have not response (404) and in Microgateway logs have not
anything, so our petitions are not correctly connected.
Please, could you help us to connect correctly Manager->Microgateway??
The text was updated successfully, but these errors were encountered: