feat: add OAuth provider HTTP flow - #1687
Draft
Zetazzz wants to merge 1 commit into
Draft
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.
Summary
authorizeandcallbackbrowser routes; consume state before handling Provider code/error and keep Provider tokens server-sideStack
Base:
feat/oauth-sso-graphql/ #1686. This is PR 5 of the OAuth/SSO platform-integration stack.The runtime operations depend on matching Tenant-private Constructive DB functions for Provider request start/read/consume and normalized identity completion. Shared Site handoff creation/redemption is intentionally PR 6; until then a successful callback uses the safe terminal success page when no continuation is returned.
Validation
@constructive-io/graphql-server: 19 suites / 167 tests@constructive-io/express-context: 5 suites / 34 testsgit diff --check