Skip to content

v2.0.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 09:21
· 5 commits to main since this release
v2.0.0
f59220f

Straza 2.0.0 is a major release. Roles can now reach down to the objects an MCP tool call works on, no credential an agent could copy is left on a person's machine, and git runs through Straza. strazad 2.0.0 refuses the 1.1.x clients, so read "Before you upgrade" first.

Highlights

Roles that cover some objects of an MCP server

Until now a role could only allow a tool, so a role that may call a write tool could call it on every object the server's credential reaches. A role can now cover some objects, such as three repositories of a GitHub organization. The server marks which argument of each tool names the object, and before any policy runs, Straza refuses a call whose argument names an object that none of the caller's roles covers, and says which objects they do cover. The console lists each server's objects, and an IGA tool such as midPoint sees each role's covers over SCIM. See Limit a role to some objects and, for server authors, Object marks.

No credential an agent can copy

straza service now holds each person's machine key, each agent's key and every session, under its own OS account on Linux, Windows and macOS. An AI agent running as the person finds nothing to copy. Each enrollment is bound to a key that never leaves the machine, and every token needs a fresh DPoP proof, so a copied token is refused. See Credentials and sessions.

Git through Straza

An agent runs plain git clone, fetch and push with no git credential on its machine. Straza decides each fetch and push with the same roles, objects, policy and approvals as an MCP call, and a push's approval names the exact refs it updates. See Git through Straza.

Packages for every machine

The client now ships as deb and rpm packages, an MSI for Windows and a macOS pkg signed with a Developer ID and notarized by Apple, each installing the background service. Guides deploy them with Intune and Jamf Pro, though no tenant has run those two guides yet.

Also new

  • Rules by tool name allow, hold or deny a harness tool that Straza does not classify, with no Straza release.
  • Browser sign-in with PKCE for straza enroll, the console and the self-service page, with guides for Keycloak, Entra ID and Okta. The Entra ID and Okta guides have not yet been run on a tenant.

Before you upgrade

Follow Upgrade from 1.1.2 to 2.0.0 in its order.
In short:

  • Register the browser sign-in addresses at your identity provider first: the console's
    /console/signin address and http://127.0.0.1/callback for straza enroll.
  • Back up the store, then upgrade strazad or the Helm chart before the machines.
  • Install the new client from its package on every machine, and every person runs straza enroll
    again. The 1.1.x client stops within five minutes of the server upgrade.
  • Enroll each AI agent again through straza service, and rotate any client secret that sat in an
    agent's environment.
  • strazactl runs on an admin API token in STRAZA_API_TOKEN. It no longer signs in, decides requests
    or publishes drafts, and a person does that in the console, on the self-service page or on the phone.
  • People enroll their own approver phones on the self-service page. Phones already enrolled keep
    working.

Security

This release fixes five vulnerabilities of 1.1.x, among them an anonymous memory exhaustion, an AI agent acting and approving in a person's name, and a removed role that kept working on a second replica. The security advisories describe each one and what to do until you upgrade. It also moves to Go 1.26.10 and go-jose 4.1.6.

Which file do I need

Each archive (.tar.gz, .zip) holds all three programs: strazad, the server, also for a standalone install on one host; strazactl, the admin CLI; and straza, the client. Each package holds only the client and installs its background service: .deb or .rpm on Linux, .msi on Windows, .pkg on macOS. On Docker or Kubernetes, run the server from ghcr.io/strazahq/straza:2.0.0 or the Helm chart.

Install and verify

Verify your download with Download a release and verify it: checksums.txt is signed with cosign, and every file below, the packages included, has its line in it. The image is ghcr.io/strazahq/straza:2.0.0, and the Helm chart is 2.0.0.

The changelog lists every change of this release.