IAM Policy Management

Today everyone is tending toward mobility and exposing their backend systems as REST APIs, which could be a result of multiple reasons. First, organizations want to use those services as reusable components across multiple departments, hence exposing them as REST APIs is a best solution. Second, organizations prefer providing their services on multiple devices and REST APIs are the best solution for devices to be accessed for services in an agnostic way. Third, in order to monetize their services by providing them publicly they would again have to do that over HTTP/HTTPS in the form of REST APIs. If the goal is to monetize by providing them to the outside world, you need a way to identify and provide access to the consumer of your services. It can be achieved by providing your consumer an identity and giving them an access to your APIs.

App42 API Gateway has the option to create IAM (Identity Access Management) users and give that IAM user access to your APIs. Once the access is given, IAM user can access the APIs by passing the required credentials along with the request. Whatever authentication policy an API provider has applied on the APIs, request would be validated as per that policy. For more information on Authentication Policies, please refer here.

API provider can also set the different traffic policy parameters for different IAMs. Traffic Policy parameters set for an IAM user would override the global settings for an API. For more information on Traffic Policies, please refer here.

Note: API access to an IAM user can be provided at granular level. You can provide access to an operation of an API while restricting the other operation of the same API.