test(oauth): cover authorize, callback, refresh routes and connector store - #18
Draft
cursor[bot] wants to merge 1 commit into
Draft
test(oauth): cover authorize, callback, refresh routes and connector store#18cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
…store Add route-level tests for session gating, PKCE cookie handling, token exchange, and refresh-token preservation to guard OAuth connector flows. Co-authored-by: esadrianno <esadrianno@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Risky behavior now covered
connectorStoreTest files added/updated
tests/api/oauth/authorize.test.tstests/api/oauth/callback.test.tstests/api/oauth/refresh.test.tstests/lib/connector-store.test.tsWhy these tests materially reduce regression risk
OAuth connector flows are security-sensitive and were only partially covered at the PKCE crypto layer. Route-level tests now guard session enforcement, state/PKCE validation, credential persistence, and refresh-token retention — the most common failure modes when wiring new connectors or changing auth middleware.