Skyflow De-identify

Third Party

De-identify and re-identifyv3.15+

Enable the Skyflow De-identify plugin with re-identification turned on.

In this configuration, Kong Gateway tokenizes outbound request bodies before proxying them upstream, and restores original values in the response before returning it to the caller. The upstream provider only ever sees tokens; the caller sees real values.

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.

The max_spans limit sets a fail-closed ceiling on how many text spans a single request may carry. Agent traffic may need a higher value because a short message can arrive alongside many resent tool definitions.

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 and Vault URL.

  • The credential’s Skyflow role permits both the de-identify and re-identify operations.

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_SERVICE_ACCOUNT_ID: Your Skyflow service account ID, used for STS token exchange.

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!