Authorize invitation history and resend for the acting team manager - #47
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.
Summary
Invitation history, invitation detail and resend now authenticate the acting user and require current
members.managefor the exact target team. Previously these routes ignored user credentials and bypassed the shared role gate. Credential-free requests now require the documented backend opt-in and origin-domain isolation.Adds 36 route regressions covering subject assertions, live membership, custom grants, stale privileges, malformed credentials and backend isolation. The API schema and integration guide document the corrected boundary and existing camelCase membership request fields.
Testing
git diff --check.