Repository navigation
Conversation
|
@eldrago4 is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
leomotors
added a commit
to leomotors/chuumai-tools
that referenced
this pull request
Oct 13, 2026
Discord now returns an RFC 9207 `iss` parameter on the authorization callback. oauth4webapi validates it against the provider issuer, but the Auth.js Discord provider declares none and falls back to the "https://authjs.dev" placeholder, so every Discord sign-in failed with "unexpected iss (issuer) response parameter value". Upstream fix: nextauthjs/next-auth#13504 (unreleased as of @auth/core 0.41.3). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Discord has started sending an RFC 9207
issparameter on the OAuth callback. Its metadata athttps://discord.com/.well-known/oauth-authorization-servernow advertises:The provider has no
issuer, sohandleOAuthfalls back to thehttps://authjs.devplaceholder andvalidateAuthResponserejects the mismatch. Every Discord sign-in fails:Setting
issuerfixes it and costs nothing: the token and userinfo URLs are already absolute, so the non-discovery branch is still taken and no extra request is made.Same failure GitHub caused in April (#13409). This is the same one-line change as #12694, which has been open since Feb 2025 — happy to close this in favour of that one if it gets picked up instead. @panva noted there that the issuer is required for the ID Token path too.