> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-code/scanning/ox-ide-integrations/configuring-cloudflare-access-for-ide-integrations.md).

# Configuring Cloudflare Access for IDE Integrations

OX supports Cloudflare Access authentication for IDE scanning requests. If your organization routes requests to OX through Cloudflare Access, configure a Cloudflare Access client ID and client secret so requests can pass through your organization's access controls.

The configuration is supported in VS Code, JetBrains IDEs, and Visual Studio.

## How Cloudflare Access authentication works

When credentials are configured, OX includes the following headers in requests to the OX backend:

| Header                    | Value                                           |
| ------------------------- | ----------------------------------------------- |
| `CF-Access-Client-Id`     | The configured Cloudflare Access client ID.     |
| `CF-Access-Client-Secret` | The configured Cloudflare Access client secret. |

Cloudflare Access validates these headers before allowing the request to reach OX.

## Prerequisites

Before configuring Cloudflare Access, make sure you have:

* An installed OX IDE extension.
* A Cloudflare Access service token with a client ID and client secret, provided by your organization's administrator.
* Access to the OX environment through your organization's Cloudflare Access configuration.

## Configuring Cloudflare Access in VS Code

**To configure Cloudflare Access credentials:**

1. Open the Command Palette:
   * Windows/Linux: `Ctrl+Shift+P`
   * macOS: `Cmd+Shift+P`
2. Select **OX: Set Cloudflare Access Credentials**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-56990a3ea1dbee13b79a52b6c0705846fb49590e%2FCloudflare1.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

3. Enter your client ID in **Cloudflare Access Client ID** (step 1 of 2) and press **Enter**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-52622d6de2ab09882b70db1c32db85cf68a8e231%2FCloudflare2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

4. Enter your client secret in **Cloudflare Access Client Secret** (step 2 of 2) and press **Enter**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-799e19e9c97baad48bc6a20a95d5fd9662c5bde1%2FCloudflare3.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

5. Verify that OX displays a credentials-saved confirmation and connects successfully.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-6d471c1775e517b8ca53fda83b93fb59f6541271%2FCloudflare4.png?alt=media" alt="" width="358"><figcaption></figcaption></figure>

## Configuring Cloudflare Access in JetBrains IDEs

JetBrains IDEs support the same Cloudflare Access credentials. The exact UI path and controls should be confirmed against the extension before publishing a detailed procedure.

## Configuring Cloudflare Access in Visual Studio

Visual Studio supports the same Cloudflare Access credentials. The exact UI path and controls should be confirmed against the extension before publishing a detailed procedure.

## Updating or removing credentials

To update credentials in VS Code, run **OX: Set Cloudflare Access Credentials** again and enter the replacement client ID and client secret.

**To remove the credentials in VS Code:**

1. Open the Command Palette.
2. Select **OX: Set Cloudflare Access Credentials**.
3. Clear the **Cloudflare Access Client ID** field and press **Enter**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-87b79c319b9c212a2dabad21ac05ebd996fe29fd%2FCloudflare5.png?alt=media" alt="" width="354"><figcaption></figcaption></figure>

OX removes the saved Cloudflare Access configuration. Subsequent requests no longer include the configured Cloudflare Access authentication headers.

## Troubleshooting

| Issue                                        | Possible cause                                                   | Recommended action                                                       |
| -------------------------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Requests are rejected by Cloudflare Access.  | The client ID or client secret is missing or incorrect.          | Verify the credentials with your administrator and configure them again. |
| IDE scans cannot connect to OX.              | Cloudflare Access authentication is required but not configured. | Configure the credentials in your IDE and retry the scan.                |
| Requests fail after credentials are updated. | The saved credentials are no longer valid.                       | Replace the existing credentials with the current service token values.  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/ox-code/scanning/ox-ide-integrations/configuring-cloudflare-access-for-ide-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
