Allow tenant invites to redirect to Lobby - #110
Open
woksin wants to merge 4 commits into
Open
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
InvitationCompletionDestinationenum (ReturnUrl/Lobby).Invite.MatchingTenantInvitationDestinationand the AspireWithMatchingTenantInvitationDestination(...)helper.ReturnUrlas the compatibility default, preserving the released matching-tenant behavior.Cratis Studio is unchanged: the invitation staging and exchange APIs and payloads are not modified.
Security boundary
This is a redirect-only setting. It changes only the destination after successful completion; invitation validation, staging, exchange, recipient binding, attestations, transaction consumption, cookies, and sessions remain unchanged. Matching tenant values do not prove which tenant issued the invitation.
Verification
ReturnUrlLobbyRelease note
Added
ReturnUrlor continue toLobby. (Successful OAuth completion should redirect to configured Lobby URL even when invite tenant matches resolved tenant #109)Security
^3.3.18, fixing GHSA-2v37-7h3g-55p8 (HIGH).persist-credentials: false.Verification audit
c3d8b25ea41a9362c942bdc7491ac6692dca21b7dba0219bab2e641eb678c4c2