Repository navigation
Releases: VoidenHQ/plugin-voiden-advanced-auth
Releases · VoidenHQ/plugin-voiden-advanced-auth
Release list
v2.0.10
Improved
- OAuth 2.0 sign-in now checks the authorization URL first and shows an error straight away when the server is unreachable or rejects the request, instead of waiting 120 seconds.
- The agent skill now explains how to tell which OAuth 2.0 grant a server offers, and when to use each one.
- The agent skill now says when to use OAuth 1.0a, and which OAuth grants are not supported.
- The agent skill now explains that all OAuth blocks in a file share one sign-in.
Fixed
- A cancelled or finished OAuth sign-in can no longer end a newer one when its timer runs out.
- The agent skill no longer suggests placing the auth block inside the request block.
- The agent skill now tells agents to use Voiden's own callback address, never a page on the API server.
v2.0.9
Fixed
- Bearer, Basic, and API key auth now send their credentials when run headlessly (voiden-runner, voiden-mcp), instead of empty values.
- Basic auth now resolves {{VARIABLES}} in the username and password when run headlessly.
- The agent skill's OAuth 2.0 examples now use valid client authentication values.
Improved
- The agent skill now explains when to use an OAuth 2.0 block and when not to, such as cookie-based logins.
- The agent skill now documents OAuth 2.0 callback URLs, automatic PKCE, token variables, and a token-request pattern for headless runs.
v2.0.8
Fixed
- The bundled skill.md now documents that all auth types (bearer, basic, apiKey, oauth1, oauth2, digest, awsSignature, ntlm, hawk, netrc, atlassianAsap, inherit/none) share one single auth block per request section. This was previously undocumented, which could lead an AI agent to insert a second auth block instead of editing the existing one when asked to change auth type.
v2.0.7
Headless Auth Now Actually Applies & Inline Block Help
Added
- The Auth block now shows an inline "?" help tooltip in its header, matching the other request blocks
Fixed
- The Auth block (Bearer, Basic, API Key) is now parsed and actually applied as request headers/query params when running headlessly via the CLI or voiden-mcp — previously nothing in the headless request-build pipeline read the auth block at all, so every CLI/MCP request silently ran with no authentication regardless of what was configured in the Auth tab, while the real Voiden app's Send button (which applies auth in the renderer before the request ever leaves it) was never affected
- Merges its auth-derived headers/query params with whatever another plugin's request-build handler already contributed (e.g. voiden-rest-api's headers-table rows) instead of overwriting them, regardless of which plugin's handler runs first
v2.0.6
fix: add borders to auth block table cells for every auth type The auth block rendered without any cell borders, unlike the other request tables (Headers, Query Params, etc.), making rows/columns hard to tell apart: - Wrap the whole block in the same bordered/rounded card used by Table.tsx. - Give OAuth2's custom key-value rows a row divider (they're plain flex divs, not real <td> elements, so they never picked up the table cell border rule). - Force a full-opacity, all-sides border on the real <table> cells used by Basic/Bearer/API Key and OAuth2's grant-fields table via a plain <style> tag instead of a Tailwind class — the host app's Tailwind build only scans apps/ui/src, never plugin source, so an arbitrary-variant class that isn't already used verbatim there is silently never compiled. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
v2.0.5
v2.0.5 — copy/paste cURL auth fixes, skill documentation expansion
v2.0.2
chore: bump to 2.0.2, document Block Overview Panel integration, void…
v2.0.1
chore: add react-markdown and remark-gfm as core shims in build config Both packages are now available via window.__voiden_shims__ from the Voiden host app. Plugins no longer need to bundle them if used. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>