Repository navigation
Windlass v0.57
Personal API tokens, viewer masking and a set of security fixes.
- API tokens. Create them in Settings and send them as a bearer token. Each has a scope and an optional expiry, and admins can revoke anyone's through the API. See the API guide.
- Viewers no longer see secret values.
.envvalues and values a Compose file sets inline are masked for the viewer role. - One instance per data directory. A second Windlass started on the same data directory now refuses to run (#43).
- Cross-origin writes are refused, and the Git token no longer appears in process arguments.
- Turning off two-factor asks for a current code.
Plugin SDK changes
Both affect plugins that use the panel's proxy.
- The proxy no longer forwards the session cookie or the
Authorizationheader to the plugin. - Anything other than GET, HEAD and OPTIONS, and any WebSocket upgrade, through the proxy now needs the member role.