Repository navigation
fix: retain provider session IDs in SDK login - #6
Merged
Merged
Conversation
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.
Keep additional ID-token scopes available so the provider can emit sid. Verify both Python and TypeScript SDK logins through the real provider and support seamless/consent redirect paths in those contracts. Validation: Linux full Go suite with dedicated PostgreSQL passed; Windows real-provider SDK contracts both passed; TypeScript SDK suite passed 34 tests. Linux SDK subprocess tests require external runtimes and were verified separately on Windows. Closes #3.