Conversation
dwaxe
force-pushed
the
dwaxe/restrict-browser-auth-origins
branch
from
September 10, 2026 20:24
3517984 to
bc25f2e
Compare
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.
Browser-session API calls currently construct their destination directly from the configured workspace URL, so a malformed or hostile value can receive the xoxc token and xoxd cookie.
This change accepts only canonical HTTPS workspace origins under slack.com, normalizes them before use, revalidates immediately before both browser transports, and rejects redirects. Standard-token routing and credential storage are unchanged.
This is the focused credential-destination portion of the earlier #128.