Beta
WSO2
Enforce centralized, contextual access policies at the WSO2 API gateway.
About PlainID + WSO2
API access control is a crucial aspect of ensuring the overall security of your APIs including the data and functionality they provide. Central to this is the need to be aware of the business context of the API usage, which includes the end-user on behalf of the request is made, and what function and data it is asked to provide.
For example, in a commercial banking application, this will mean making a decision based on the bank teller who's trying to access the bank account, which branch he is part of, what is his title, etc. And the actual bank account he is asking to access, the type or status of the account, and more.
The decision can’t be based just on the service account that is using that specific API. Though API Gateways do have access control capabilities, usually they are unaware of the context (i.e. will make a decision to determine if a call for a service can be made, and not based on the specific context of the call), and whatever identity-awareness they might have is limited and hard to manage.
Without contextual and identity-aware measures in place, there are significant risks associated with unauthorized access to the data through APIs.
PlainID Authorizer for Azure WSO2 API gateways provides the API gateway with context awareness, of the identity and the assets the identity is trying to access.
Technical Information
The WSO2 API Gateway authorizer is compatible with the regular WSO2 API Manager or the Choreo Connect API Gateway.
The PlainID Authorizer is deployed as a host-level daemon or a side-car container that the gateway will query during an access request.
Architectures
- The end user access the application.
- The user is redirected to complete the authentication process on the Identity Provider (IdP).
- The API call is intercepted by WSO2 API GW.
- The API Gateway calls the PlainID Authorizer for an access decision using the Validate Request configuration. The Authorizer queries the PDP for a policy-based decision, which is dynamically calculated and enforced at the API Gateway as permit or deny.
- The client can access API resources and services.
Technology
- API Gateways
Capabilities
- Manage
- Enforce
Auth Patterns
- API Authorization
Need help integrating?
Our experts can help you architect the perfect authorization strategy for your stack.
Better Together
Connect Context. Centralize Policy. Enforce Everywhere.


