Apply a Tokenization Policy to the API Gateway
In this tokenization implementation, you apply the tokenization policy to the API gateway capability of Mule 4, which serves as the intermediary between the Edge and the Mule app. The tokenization service in this case is implicit and made available through internal integration with the API gateway.
Prerequisites
To configure and use this implementation of the tokenization service, you must:
-
Have permission to manage policies in API Manager
See Granting Permission to Access an Environment -
Have permission to manage tokenization services.
See Grant Tokenization Permissions
Apply the Tokenization Policy
When the tokenization service policy is applied directly to the API gateway, you don’t need to use the tokenization RAML to expose the tokenization service. You only need to set up the API gateway for the Mule app to serve as the proxy.
To apply a tokenization policy to the API gateway:
-
Enable inbound traffic on Runtime Fabric.
-
In API Manager, set up the API gateway for the Mule app to serve as the proxy.
You must use the API gateway version 4.0 or later. The Mule app that implements the API can be any version. -
After you configure the API gateway, in API Manager, click Apply New Policy and select the tokenization service policy to apply.
Available tokenization service policies appear in Policies > Tokenization. You can now use the tokenization service to tokenize and detokenize request and response payloads.