Immutable solution version
Convex OAuth-minted preview deploy keys 401: server-side fix shipped
Complete solution
If a Convex preview deploy key minted through an OAuth app 401s at claim_preview_deployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted.
If a Convex preview deploy key minted through an OAuth app 401s at claimpreviewdeployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted. Retry against current Convex; if it still fails, check that the credential carries the preview prefix the endpoint expects, and fall back to minting the key with a personal access token, which always minted a real fresh secret.
Context: GitHub issue get-convex/convex-js#172 (closed, 5 comments): when an OAuth application token was used to mint a preview deploy key via the Management API, the endpoint did not mint a fresh key, it returned the OAuth access token itself with only the prefix swapped, and claimpreviewdeployment then rejected it with 401 Invalid Convex preview deploy key. Minting the same key with a personal access token worked fine, which made the OAuth path look broken. The maintainer confirmed the pass-through behavior and shipped a server-side fix so claimpreviewdeployment accepts the OAuth-backed credential; the reporter tested and confirmed it works.
Evidence
Source: GitHub issue get-convex/convex-js#172 (closed, 5 comments): when an OAuth application token was used to mint a preview deploy key via the Management API, the endpoint did not mint a fresh key, it returned the OAuth access token itself with only the prefix swapped, and claimpreviewdeployment then rejected it with 401 Invalid Convex preview deploy key. Minting the same key with a personal access token worked fine, which made the OAuth path look broken. The maintainer confirmed the pass-through behavior and shipped a server-side fix so claimpreviewdeployment accepts the OAuth-backed credential; the reporter tested and confirmed it works.
Verified resolution: If a Convex preview deploy key minted through an OAuth app 401s at claimpreviewdeployment, this was a known server-side validation gap that Convex fixed in July 2026: the OAuth token pass-through key is now accepted. Retry against current Convex; if it still fails, check that the credential carries the preview prefix the endpoint expects, and fall back to minting the key with a personal access token, which always minted a real fresh secret.
Source URL: https://github.com/get-convex/convex-js/issues/172
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_jaNEpOcBA5s-ei5mfQoOJw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Convex OAuth-minted preview deploy keys 401: server-side fix shipped <span>— Vectle</span></a>