DEV Community

Ioneyrezende
Ioneyrezende

Posted on

Windmill tokens carry user authority unless scopes stop them

Windmill tokens carry user authority unless scopes stop them

Windmill runs scripts, flows, schedules, and apps across workspaces. Its API is designed to be automated, which makes token scope and workspace membership central security controls. A token is not merely an API convenience. It represents a user identity and the permissions that identity can exercise.

A count-only ZoomEye query on 2026-11-21 returned three matches for app="Windmill" and 2,509 for title="Windmill". Both used sub_type=all, page 1, and page size 1. The application count is small and may miss deployments. The title count is broad and may include unrelated pages. Neither is a confirmed deployment or vulnerability count.

Windmill documentation says that user tokens authenticate API requests and that a token inherits the full permissions of the user who created it by default. The operator can limit token permissions to specific scopes. The token is shown only once at creation, and an administrator can impose a maximum expiration. A workspace member may start with no access to existing folders; access is granted through folders, groups, and roles.

That model creates three review questions. Which user created the token? What workspace roles and folder permissions does that user have? Which scopes are attached to the token? If a service token belongs to an administrator, a narrow scope list is still important because future API paths may be added. If the token belongs to a developer with access to production flows, removing a role from the person does not automatically remove the token unless the account is disabled or the token is revoked.

Workspace isolation is separate from instance administration. A user can be a member of several workspaces, and a token can be used against a workspace path. Test that a token from workspace A is rejected by workspace B. Test a run endpoint with a token that lacks execution permission. Verify that HTTP trigger authentication checks the required trigger scope rather than accepting any valid bearer token.

Keep tokens out of browser code and logs. Store them in a secret manager or a workload identity facility. Use separate tokens for deployment, read-only reporting, and run execution. Set expiration dates where the platform supports them. When a user leaves, disable the account and revoke tokens. When a group loses access, re-test the script or flow path that used that group.

The external count should be reconciled with the organization's hostnames and deployment inventory. A Windmill title page may be a public app, documentation, or an unrelated site. Do not create a workspace, submit a script, or probe tokens. For an owned instance, the operator can verify the token owner, scopes, workspace role, folder grants, and trigger authentication from the administrative interface and API logs.

Windmill is powerful because it lets teams compose automation quickly. The token should carry exactly the authority required for its job, no more and no less.

Exact query: title="Windmill"

Open the normalized ZoomEye search

References

Top comments (0)