v1.12.2
Discover the new features, logic changes, bug fixes, breaking changes, and known issues and limitations in this Piiano Vault release.
New features
- A new JWT enforcer type:
https://app.piiano.io/prop-claim-ref
that allows you to reference a claim from the JWT token as the value of a property enforcement. See Namespace claims for more information. - Namespace claims can now be nested in one another. For example, placing an
all-of
claim inside anany-of
claim. - Direct JWT authentication now supports a new configuration:
extra_claims
. This configuration allows you to add extra claims (statically configured in the IAM) to be attached to the JWT token when it is being sent to the Vault. See Configure JWT Authentication for more information. - Direct JWT authentication now supports a new configuration:
namespace_top_claim
. This configuration is used to specify the top claim in the JWT token that contains the namespace claims. See Configure JWT Authentication for more information. - A new JWT enforcer type:
https://app.piiano.io/all-of
that requires all the properties in the claim to be enforced. Although it is the default behavior, it is helpful if nested under other enforcer expressions such asany-of
. See Namespace claims for more information. - JWT enforcers
https://app.piiano.io/any-of
andhttps://app.piiano.io/all-of
supports an optional identifier to allow multiple enforcers of the same type at the same level. See Namespace claims for more information.
Logic changes
- JSON data type now accepts all valid JSON values, including an array, string, number, object, etc. Previously, it only accepted an object.