Connection for Next-Gen Trust Security releases¶

Learn about current and past releases of Connection for Next-Gen Trust Security.

The Helm charts for Connection for Next-Gen Trust Security are public.

Release 0.7.0¶

Connection for Next-Gen Trust Security v0.7.0 was released on 13 October, 2026.

Key features¶

• You can now set spec.ngts.workspaceID to authenticate with a Built-in Account that belongs to a workspace. See Authenticate to Next-Gen Trust Security with Workload Identity Federation.
• You can now set zone to a request policy ID, as well as a request policy name.

Fixes and updates¶

• If more than one request policy matches the name in zone, the request now fails with an error. Previously, Connection resource picked one of the request policies. To fix the error, rename one of the request policies, or set zone to the ID of the one you want.
• Fixed zone so that it accepts the request policy name on its own. In v0.6.0, zone also required an application name.
• Updated Go to 1.27.2 and golang.org/x/net to v0.60.0 to fix security vulnerabilities.

Downloads¶

• Helm chart: oci://registry.ngts.paloaltonetworks.com/charts/venafi-connection:v0.7.0

Release 0.6.0¶

Connection for Next-Gen Trust Security v0.6.0 was released on 30 April, 2026.

Key features¶

• You can now configure a VenafiConnection resource to authenticate to Next-Gen Trust Security using a Tenant Service Group ID (tsgID) and private key JSON Web Token (JWT). See Authenticate to Next-Gen Trust Security with a private key.
• In the custom resource definition, Firefly has been renamed to Distributed Issuer and you can now use spec.distributedIssuer as an alias for spec.firefly.
• The vCert library is now included directly in the codebase, removing it as an external dependency.

Downloads¶

• Helm chart: oci://registry.ngts.paloaltonetworks.com/charts/venafi-connection:v0.6.0