-
Notifications
You must be signed in to change notification settings - Fork 7
feat(security): per-tool approver allowlist for DEFER approvals (email-based, fail-closed) (#313) #315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+903
−71
Merged
feat(security): per-tool approver allowlist for DEFER approvals (email-based, fail-closed) (#313) #315
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
514ff2d
feat(security): per-tool approver allowlist for DEFER approvals (emai…
initializ-mk 2cad19a
feat(slack): reject-reason modal for DEFER approvals (#313)
initializ-mk eb2bf44
docs+validate(defer): caller-asserted-email note + approver-typo warn…
initializ-mk 2783b66
docs(defer): correct approver-warning example — structural check, not…
initializ-mk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor (threat-model clarity): state that the email is caller-asserted — its strength differs by path.
The allowlist authorizes an asserted email, and its trustworthiness comes entirely from who asserts it:
users.info, bound to the authenticated Slack identity. This is the strong path — the one that was vulnerable in feat(channels): native Slack interactive approvals for DEFER (R4c) (#310) #311 — so the gate genuinely restricts which channel members can approve.approver_email, including a listed one. Acceptable (the token holder is already trusted), but it means the direct path's real gate is the endpoint's authentication, and the allowlist is advisory there.This section documents the config, the
users:read.emailscope, and fail-closed, but never states this distinction — an operator could assume the email is always verified. Suggest a paragraph: "The Slack adapter resolves the approver's email from their authenticated Slack identity; a directPOST /tasks/{id}/decisionstrusts theapprover_emailthe (authenticated) caller supplies — so the endpoint's bearer auth is the gate for direct posts." Worth a corollary line: don't run--no-authwith an allowlist and expect it to hold (no auth ⇒ anyone reaching the port asserts any email).