Included Policies Directory
Availability by Gateway
Policy | Flex Gateway | Mule Gateway | Summary |
---|---|---|---|
✓ |
✓ |
Allows access based on the basic authorization mechanism, with user-password defined on LDAP |
|
✓ |
✓ |
Allows access based on the basic authorization mechanism, with a single user-password |
|
✓ |
✓ |
Allows access only to authorized client applications |
|
✓ |
✓ |
Enables access to resources residing in external domains |
|
✓ |
Returns a tokenized value to its original value |
||
✓ |
✓ |
Adds headers to a request or a response |
|
✓ |
✓ |
Removes headers from a request or a response |
|
✓ |
✓ |
Caches HTTP responses from an API implementation |
|
✓ |
✓ |
Allows a list or range of specified IP addresses to request access |
|
✓ |
✓ |
Blocks a single IP address or a range of IP addresses from accessing an API endpoint |
|
✓ |
Protects against malicious JSON in API requests |
||
✓ |
✓ |
Validates a JWT |
|
✓ |
✓ |
Logs custom messages using information from incoming requests, responses from the backend, or information from other policies applied to the same API endpoint |
|
OAuth 2.0 Access Token Enforcement Using Mule OAuth Provider |
✓ |
Allows access only to authorized client applications |
|
✓ |
Allows access only to authorized client applications |
||
✓ |
Allows access only to authorized client applications |
||
✓ |
✓ |
Allows access only to authorized client applications |
|
✓ |
Allows access only to authorized client applications |
||
✓ |
✓ |
Monitors access to an API by defining the maximum number of requests processed within a period of time |
|
✓ |
✓ |
Monitors access to an API by defining the maximum number of requests processed within a timespan, based on SLAs |
|
✓ |
✓ |
Regulates API traffic |
|
✓ |
Enables HTTPS |
||
✓ |
Transforms sensitive data into a nonsensitive equivalent, named token |
||
✓ |
Protects against malicious XML in API requests |