Mailgun Webhooks Not Working If Webhook Signing Key Differs From API Key

[mkinyon]

Description

Submitted on behalf of Whitewater Crossing Church.

Email tracking with the Mailgun HTTP transport will not work if the HTTP webhook signing key and the API key are not the same. (The API key is used for sending email and the HTTP webhook signing key is used for email tracking.) These keys can get out of sync if a new API key is created or if the webhook signing key gets refreshed. Also, it doesn't seem possible to get these keys back in sync after one has been changed.

Actual Behavior

If the API key and HTTP webhook signing key differ in Mailgun, then either email sending or email tracking is not working depending on which key is entered into the Mailgun HTTP transport.

Expected Behavior

I would expect the Mailgun HTTP transport to have two settings for the API key instead of one. One for the API key and the other for the webhook signing key.

Steps to Reproduce

• You will need a Mailgun account configured with an API key that is different than the HTTP webhook signing key.
• If you put the API Key into the Mailgun HTTP transport settings, you can only send email without email tracking.
• If you use the Webhook signing key, then email tracking works but sending communications causes an unauthorized error.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug or enhancement is already reported.
• Try to reproduce the problem on a fresh install or on the demo site.

Rock Version

v14.3

Client Culture Setting

en-US

[nairdo]

Thanks @mkinyon . We also discovered this late last week and have patches coming in Rock v14.4, v15.4, and v16.1.

[Update -- I should have also mentioned that it appears Mailgun semi-recently changed their UI which means both new customers and existing customers who recycle their keys will fall into this problem situation which requires the patch.]