chore(auth): diagnose unexpected managed OAuth callback failures - #7896
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
icecrasher321
marked this pull request as ready for review
September 16, 2026 22:36
Contributor
|
This branch was previously 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
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.
GitHub Search account connections on dev fail in both the installation setup and individual enrollment paths, but the callback currently records only
errorClass: unexpected. This hides the distinction between session authentication, enrollment authentication, and authorization completion failures.Add the failing callback stage, an allowlisted underlying error type, a message fingerprint, and a bounded database error code to unexpected-error diagnostics. Reuse the shared cause-chain describer; raw messages, SQL parameters, provider responses, and credentials are not logged. Tests cover wrapped database errors, arbitrary private error metadata, and both installation callback stages.
This is a diagnostic change. It needs a dev deployment and another connection attempt before the underlying authorization failure can be identified.
Validation: 52 focused callback/redirect tests passed; app type check, API validation audit, Biome, and diff checks passed.