Apigee-PCF route service with microgateway

[#1]

We are doing some POC on using Apigee microgateway with PCF on-premise environment but encountering some issues.

Let’s say, we have already put an echo app on PCF with some URL “http://xxxxxx.spi-pcf.example.com/mgpoc/” which just has dummy echo logic.

Our local microgateway.

We already setup the apigee microgateway on our own PC. And We are able to call the echo app through this local microgateway with a “x-api-key”.

GET http://<my PC’s microgateway>/mgpoc/

x-api-key: Ryx….

I can call the app through this local microgateway with a authorization bearer token as well like this:

GET http://<my PC’s microgateway>/mgpoc/

Authorization: Bearer eyJhb…..

Microgateway on PCF

We also deployed the microgateway on PCF as app instance and it is find as well.

GET http://<PCF microgateway app>/mgpoc/

x-api-key: Ryx….

GET http://<PCF microgateway app>/mgpoc/

Authorization: Bearer eyJhb…..

Both calls are OK.

Failed when trying with PCF-apigee routing service broker

However, we tried following the apigee docs to setup PCF apigee route service (microgateway) and binding the app to the route service

https://github.com/apigee/pivotal-cf-apigee/tree/master/apigee-cf-service-broker#microgateway

And then we call the echo app again, it would failed.

HTTP/1.1 401 Unauthorized
Content-Length: 84
Content-Type: application/json
X-Vcap-Request-Id: ....

{
"error": "missing_authorization",
"error_description": "Missing Authorization header"
}

It said that 401 unauthorized and ask me to put the authorization header.

We tried again to call by passing “x-api-key: …” or “Authorization: Bearer …” headers. But it is always returning 403 Forbidden like this:

HTTP/1.1 403 Forbidden
Content-Type: application/json
X-Response-Time: 1757
X-Vcap-Request-Id: ....
Content-Length: 25

{
"error": "access_denied"
}

Do you know any reason why after we binded the app to the route-service, the app service call with API key/Authorization header would have the 403 access denied error?