v1.11.0

Discover the new features, logic changes, bug fixes, breaking changes, and known issues and limitations in this Piiano Vault release.

New features

• Direct JWT authentication now supports extra claims validation using the bound_claims configuration. See JWT configuration in the IAM file for more information.
• Direct JWT authentication now supports the jwks_uri configuration. When configured, Vault fetches and regularly refresh the key sets from the provided URI. See JWT configuration in the IAM file for more information.
• Update Token API now supports updating the data of the token, while keeping the token ID the same. See Update Token for more information.
• Update Token API now supports the ensure-unique-tenant-tags optional parameter. Like with Tokenize, this parameter ensures that the tags provided are unique in the tanant level. See Update Token for more information.
• New REST API endpoint set-admin-api-key to set the API key of the admin user. See Set Admin API Key for more information.

Logic changes

• Direct JWT authentication no longer requires the kid configuration. Vault uses the kid claim in the JWT token to decide which key to use for verification. See JWT configuration in the IAM file for more information.

Breaking changes

• CLI flag ensure_unique_tenant_tags of Tokenize was renamed to ensure-unique-tenant-tags.