What's new

Release notes for the core platform and the modules, newest first.

Webhook Engine

Webhook Engine 2.3

On Destinations, Delivery Logs and the Test Console, the ? Help link now opens the Help Center article for that screen.

New

  • On Destinations, Delivery Logs and a destination's Test Console, the ? icon in the header opens the Help Center at the article for that screen, instead of the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Webhook Engine

Webhook Engine 2.2

Sign the timestamp protects deliveries against replay. It's on for new destinations, and off for existing ones until you switch it on.

New

  • Sign the timestamp, a setting on each destination. When it's on, the signature covers the delivery's timestamp as well as its payload, and deliveries say they use signature version 2. When it's off, deliveries are signed exactly as before. See Add a webhook destination.
  • With version 2, each attempt is signed when it's sent, so a delivery that was held back or retried carries a fresh timestamp and isn't mistaken for a replay. See Verify webhook signatures and handle retries.
  • The Test Console signs tests the way the destination does, and shows which way beside the destination's status. See Test a webhook destination.

Fixed

  • A failed attempt counts once. It used to be logged twice and counted twice, so a destination was suspended after 10 failed attempts instead of 20. See Deliveries fail or a destination is suspended.
  • A delivery to a destination deleted after it was queued no longer ends as a failed job. A destination in the trash is skipped, and one deleted for good is dropped.
  • Deliveries carry the installed Webhook Engine version in their User-Agent header. It always said 1.0.0. See Webhook payloads, headers and events.

Security

  • Deliveries can be protected against replay. Before, the timestamp wasn't signed, so a captured delivery passed the check every time it was resent. With Sign the timestamp on, a receiver can refuse a delivery whose timestamp is too old.
  • Sign the timestamp is on for every destination you create from now on, and off for every destination you already had, so no receiver starts failing when you upgrade. To protect an existing destination, have its receiver updated to accept version 2, then switch the setting on.
  • An unused API address is gone. Any API token could call it without a permission check, and it returned the caller's own user account. Nothing used it.