> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/security/origin-basic-authentication.md).

# Origin Basic Authentication

Authenticate CDN requests to your origin using HTTP Basic Authentication.

**Origin Basic Authentication** allows the CDN to include HTTP Basic Authentication credentials in requests sent to your origin server. This enables the CDN to access origins protected by HTTP Basic Authentication without exposing the configured credentials to end users.

Origin Basic Authentication is configured for Dynamic CDN Resources in the [Medianova Control Panel](https://cloud.medianova.com).

{% hint style="info" %}
Origin Basic Authentication affects only communication between the CDN and your origin server. It does not affect requests between end users and the CDN.
{% endhint %}

## Configure Origin Basic Authentication

{% stepper %}
{% step %}

### Open Security

Open the Dynamic CDN Resource that you want to configure and select **Security**.
{% endstep %}

{% step %}

### Enable Origin Basic Authentication

Turn on **Origin Basic Authentication**.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FZH04A88oKiaVT6JTNFyt%2Fimage.png?alt=media&amp;token=cbcbd64c-ce8e-48f5-a695-b3a150fce662" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enter the Origin Credentials

Enter the HTTP Basic Authentication credentials expected by your origin server:

* **Username** — Enter the username configured on the origin.
* **Password** — Enter the corresponding password.

The configured credentials are included in each CDN-to-origin request.
{% endstep %}

{% step %}

### Save the Configuration

Select **Save** in the pending changes bar.

Review the pending changes and confirm the configuration.
{% endstep %}
{% endstepper %}

## How Origin Basic Authentication Works

When Origin Basic Authentication is enabled, the CDN includes the configured HTTP Basic Authentication credentials in requests sent to the origin server.

{% hint style="info" %}
This behavior applies only to CDN-to-origin communication. Requests between end users and the CDN are not affected by this setting.
{% endhint %}

## Important Notes

* The username and password must match the HTTP Basic Authentication credentials expected by the origin server.
* Incorrect credentials can cause origin requests to fail authentication.
* The configured credentials are included in each CDN-to-origin request.
* Updating the credentials requires saving the CDN Resource configuration again.

## Related Concepts

* [Origin Basic Authentication API](/api-documentation/security/origin-basic-authentication.md)
* [Security](/products/security.md)


---

# 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://clients.medianova.com/products/security/origin-basic-authentication.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.
