From ffc20d2bf66722c619946ffe9fe71e04a83183bf Mon Sep 17 00:00:00 2001 From: Marek Isalski Date: Sun, 13 Feb 2022 12:06:11 +0000 Subject: [PATCH] Atlassian list a specific set of IPs for outgoing connections --- docs/Hook-Examples.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Hook-Examples.md b/docs/Hook-Examples.md index 1aefe8a..00b7f36 100644 --- a/docs/Hook-Examples.md +++ b/docs/Hook-Examples.md @@ -83,7 +83,7 @@ This example works on 2.8+ versions of Webhook - if you are on a previous series ## Incoming Bitbucket webhook -Bitbucket does not pass any secrets back to the webhook. [Per their documentation](https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html#Managewebhooks-trigger_webhookTriggeringwebhooks), in order to verify that the webhook came from Bitbucket you must whitelist the IP range `104.192.143.0/24`: +Bitbucket does not pass any secrets back to the webhook. [Per their documentation](https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#Outgoing-Connections), in order to verify that the webhook came from Bitbucket you must whitelist the IP range `104.192.143.0/24`: ```json [