Use webhook signing key instead of API key for webhook signature verification #819
+7
−7
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.
When instantiating a
Mailgun
instance you are expected to provide an API key that is used to authenticate requests to the REST API.This API key was passed to the
Api\Webhook
instance that is instantiated via$mg->webhooks()
.https://github.com/mailgun/mailgun-php/blob/master/src/Mailgun.php#L142
This passed API key is used in the
verifyWebhookSignature
function.This will result in improper verification results as the account webhook signing key should be used to compute the signature, not the REST API key.
As is, you must manually instantiate an
Api\Webhook
instance to provide a webhook signing key and properly validate webhook signatures using this library.This PR allows for passing a webhook signing key using the
$mg->webhooks('signing-key')
function.