Automattic / Automattic/jetpack

Auto-detect Zapier requests in Jetpack Protect

Open
#14,078 4 comments 2 reactions 0 assignees View on GitHub
[Feature] Protect Customer Report [LEGACY] Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

#### Is your feature request related to a problem? Please describe.

I’ve been running into repeated issues with blocked IP addresses when using Zapier, which is a tool I frequently use to automate tasks like uploading posts and images to our self-hosted site. As explained here, Zapier uses a range of IP addresses every time it launches a new task: https://zapier.com/help/troubleshoot/behavior/cant-access-or-use-zapier-with-other-apps

#### Describe the solution you'd like

I’d like to see Jetpack Protect auto-detect the use of IP addresses from Zapier, potentially through an upgraded integration.

#### Describe alternatives you've considered

I’ve looked into blocking IP addresses, but the range it uses is too broad. I could use Cloudflare to block login attempts instead.

#### Additional context

Here’s a screenshot of the error I receive in Zapier when this error arises:

![Screenshot 2019-11-19 17 13 07](https://user-images.githubusercontent.com/470216/69196222-d41d9900-0afb-11ea-8c7d-f358d17fcb77.png)

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Start by locating Jetpack Protect's IP-blocking logic and reviewing how Zapier requests are identified, then clarify the supported detection approach and integration boundaries. Done should include an agreed implementation scope and tests covering Zapier-originated requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.