processes that run on the organization's on-premises Secure Agent. Use the API Microgateway Service to expose managed APIs as API Microgateway proxies.
You can use the following methods to control access to managed APIs that you publish with the API Microgateway Service:
IP filtering policy
Rate limit policy
Basic authentication or OAuth 2.0 authentication
The API Microgateway Service provides REST APIs to create and deploy API Microgateway proxies. API consumers access the managed APIs deployed as API Microgateway proxies on the organization's on-premises environment. The
Application Integration
processes expose REST Service URL and SOAP Service URL endpoints.
Use the API Microgateway Service to build an API Microgateway proxy to an API endpoint to manage. The API Microgateway Service builds an API Microgateway as an immutable Docker image on the organization's Secure Agent machine. You then use the API Microgateway Service to deploy the Docker image in a container on the Secure Agent Docker runtime environment for API access. The API Microgateway applies the API access policies that you configure before forwarding the requests to
Application Integration
endpoints.
The following diagram shows the API Microgateway Service and API Microgateway components exposing a managed API in the on-premises environment:
The Secure Agent Docker runtime environment hosts the Docker images using the blue-green deployment strategy to provide zero downtime during updates of the API Microgateway component.
ASK INFAPreview
