Use JWT gem for Webhook signature validation #71
Merged
Conversation
This file contains 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.
Fixes #70
At this moment, the
ibanitygem uses thejosegem for JWT signature validation of incoming webhooks.The
josegem is not compatible with Ruby installations compiled against OpenSSL 3, e.g. potatosalad/ruby-jose#19, which means that theibanitygem cannot validate webhooks for Ruby installations using OpenSSL 3.This PR removes the dependency on the
josegem and uses the better maintainedjwtgem that is in fact OpenSSL 3 compatible. A spec was added to verify that the behaviour mostly stays the same, returningIbanity::Errors for signature validation failures.