> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Protection Bypass for Automation
- URL: https://blog.esadax.com/en/protection-bypass-for-automation/
- Published: 2026-11-15T04:21:11.000Z
- Updated: 2026-11-15T04:21:11.000Z
- Author: Esadax 
- Tags: #tr-platform-17-security-16-protection-bypass-automation, #en, #mdx-imported, Platform

## Overview

Esadax's Protection Bypass for Automation feature allows you to temporarily bypass deployment protection mechanisms, such as password protection, authentication, and trusted IPs, for automated tools like end-to-end testing. This is particularly useful when automating processes that require access to your application.

---

## Table of Contents

1. [Compliance Measures](#compliance-measures)
2. [Methods to Bypass Deployment Protection](#methods-to-bypass-deployment-protection)
3. [Protection Bypass for Automation](#protection-bypass-for-automation)
4. [How-to Protection Bypass for Automation](#how-to-protection-bypass-for-automation)

---

## Compliance Measures

- **Shared Responsibility**: Ensure that compliance measures are shared between your team and Esadax.
- **Firewall Access Control**: Implement strict firewall rules to control access to sensitive areas.
- **SAML/SSO**: Use Single Sign-On (SSO) solutions for secure authentication.
- **HTTPS/SSL**: Enforce HTTPS to secure data in transit.
- **Directory Sync**: Synchronize directories for user management.

---

## Methods to Bypass Deployment Protection

- **Password Protection**: Temporarily disable or bypass password protection for automated tools.
- **Esadax Authentication**: Use generated secrets to bypass Esadax's authentication layer.
- **Trusted IPs**: Extend trusted IP ranges for testing environments.

---

## Protection Bypass for Automation

- **Generated Secret**: A secret value is created to bypass deployment protection.
- **System Environment Variable**: The secret is automatically added as `Esadax_AUTOMATION_BYPASS_SECRET` to your deployments.
- **Redeployment Requirement**: Updating the secret will require redeploying your application.

---

## Who Can Manage Protection Bypass for Automation?

- **Team Members**: Those with at least the "Member" role can manage bypass settings.
- **Project Administrators**: Users with the "Project Administrator" role have full control.

---

## Using Protection Bypass for Automation

1. **Optional Advanced Configuration**:

**SameSite Configuration**: For iframe scenarios, set `samesitenone`.

```text
x-esadax-set-bypass-cookie: samesitenone

```

**Cookie Bypass**: Set `x-esadax-set-bypass-cookie` to `true` for in-browser testing.

```text
x-esadax-set-bypass-cookie: true

```

**Set Header or Query Parameter**: Use `x-esadax-protection-bypass` header or query parameter with your generated secret.

```text
x-esadax-protection-bypass: your-generated-secret

```

---

## Example: Playwright Configuration

```typescript
const config: PlaywrightTestConfig = {
  use: {
    extraHTTPHeaders: {
      'x-esadax-protection-bypass': process.env.Esadax_AUTOMATION_BYPASS_SECRET,
      'x-esadax-set-bypass-cookie': true | 'samesitenone' // optional
    }
  }
};

```

---

## Last Updated