Windmill replaces stored Anthropic keys with temporary user identity
Windmill 1.849.0 introduces per-user identity federation for its AI chat and copilot connection to Anthropic. Signed identity tokens are exchanged for access tokens, avoiding a persistent Anthropic key in that connection. Billing still uses a shared service account, and scripts and agent steps remain outside the feature. Windmill says successful end-to-end federation with a real organisation remains untested.
Artificial Intelligence··Midday
User tokens replace a persistent key
Windmill’s new Anthropic connection uses signed OIDC identity tokens carrying a user’s email and workspace information. These are exchanged for access tokens, with a default identity-token lifetime of thirty minutes. Version 1.849.0, released on 25 October, brings this per-user federation to Windmill AI chat and copilot. The connection therefore no longer needs to store a persistent Anthropic key for those tools.[1]
Billing stays with the shared account
Authentication history retains individual user identity, but spending still belongs to the shared service account linked to the federation rule. It does not move to each person’s separate subscription. Cached credentials are separated by workspace, configuration and email address, and refreshed before expiration. Only api.anthropic.com is accepted as the destination, excluding custom host addresses that could send identity tokens to another server.[1]
Scripts remain outside the connection
The federation resource is refused by scripts as well as agent steps; both still require the key-based routes they already support. The implementation requires an enterprise OIDC licence. Its developer tested successful token exchanges with a stub service, but says no real organisation has yet completed a successfully tested end-to-end exchange. A real-endpoint request with invented identifiers was rejected. This single project document establishes the release’s scope and disclosed testing limits.[1]