Ozair Sheikh

Enhancing the REST Management API

1

Enhance the REST management API to allow additional flexibility to configure the API gateway without the need for the API Connect toolkit.

Need to fix deprecated loopback use

1

Clean up warnings during `npm install`

Microgateway terminates when publishing mixed http and https schemas

1

uGW will terminate if schemes on 1/x apis is http.. and the rest are https.

Single docker image for node.js and ngnix

1

The current API microgateway combines ngnix and node.js using a docker compose file, which results in two separate container instances. We should use a single docker image that runs both...

Breaking up the preflow middleware so that the swagger security code is in its own middleware, which presumably would run between the existing preflow and the flow engine.

Automate the pulling of external policies into the micro-gateway project along with ensuring that the micro-gateway is correctly configured to consume and run the policy.

Presently, the µgw uses 2 middlewares to pre-populate APIC context variables: - The `context` middleware: for "general" context vars (system, request, and message metadata) - The `preflow` middleware: handles apiconnect-specific...

Currently the authenticated username for a request ends up in client.org.id for basicAuth or `oauth.resource-owner` for oAuth. This makes identity propagation a challenge because there is no reasonable default for...

The API Connect toolkit provides an embedded microgateway available from npm. It should be updated to use the docker-based microgateway with ngnix and node.js.

This pollutes the startup logs