This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
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.
Add support for Slack shared secret message signing #30
Add support for Slack shared secret message signing #30
Changes from all commits
27138be
895d55c
e7d8c1a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
That code is used in multiple endpoint. I would be best to take it out in a function, something like
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.
I chose to explicitly keep
verification_token
as a new variable so the token we're passing intoEvent
is explicitlyNone
when thesigning_secret
is set. This way we're not relying on the initialization behavior inslack/plugin.py
. If we wanted to rely on no one tampering with theslack.verify
parameter then we could just callvalidate_request_signature
rather than wrapping it in avalidate_request
function.