Skyflow De-identify

Third Party

De-identify onlyv3.15+

Enable the Skyflow De-identify plugin with re-identification disabled.

In this configuration, the plugin tokenizes outbound request bodies before Kong Gateway proxies them upstream. Re-identification is off, so the caller also receives tokens rather than restored values. Use this configuration for a strict egress posture where no original values should leave your trust boundary.

The sts credential method requires no stored Skyflow secret. Kong Gateway exchanges each caller’s own identity provider (IdP) token for a short-lived Skyflow bearer token using RFC 8693 token exchange.

Prerequisites

  • The Skyflow De-identify plugin is installed.

  • You have a Skyflow account with a Detect vault. From the vault’s page in the Skyflow admin console, copy the Vault ID, Vault URL, and Account ID.

  • The credential’s Skyflow role permits the de-identify operation.

Environment variables

  • SKYFLOW_VAULT_ID: The ID of your Skyflow Detect vault.

  • SKYFLOW_VAULT_URL: The full URL of your Skyflow vault. For example: https://{cluster}.vault.skyflowapis.com. Sandbox vaults use .skyflowapis.tech.

  • SKYFLOW_ACCOUNT_ID: Your Skyflow account ID.

  • SKYFLOW_SERVICE_ACCOUNT_ID: Your Skyflow service account ID, used for STS token exchange.

  • SKYFLOW_EXPECTED_ISSUER: The issuer URL of your IdP. For example: https://login.microsoftonline.com/{tenant}/v2.0.

  • SKYFLOW_EXPECTED_AUDIENCE: The expected audience value in the caller’s IdP token. Typically the client ID of your IdP application.

Set up the plugin

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!