> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/schema-registry/manage-security/basic-authentication.md).
# Basic Authentication
Basic Authentication is currently supported for WarpStream BYOC Schema Registry. When basic authentication is enabled, the WarpStream Agent uses the username/password encoded in the HTTP request's Authorization header to authenticate your Schema Registry clients.
## Creating Credentials
To obtain a username/password to use with your schema registry client, you'll need to create a set of credentials. You can do that by navigating to the "Credentials" view of the [WarpStream Console](https://console.warpstream.com/schema_registries) for your schema registry cluster.
You can then click on the "Create Credentials" button and follow the wizard to create the credential. Once a credentical is created, the admin page will display the created username and password. You must store them somewhere safe right away, as you'll never be able to view them again. WarpStream does not store them in plaintext, so we cannot retrieve them for you.
In the case that you lose your credentials, you can create a new set of credentials in the admin console following the same steps as above, up to a limit of 100 credentials.
\
Configure WarpStream Agents
--------------------------------------------------------------------------------------------------------
To enable basic authentication for your Schema Registry Agents, set the `schemaRegistryBasicAuth`flag. Alternatively, you can set the environment variable `WARPSTREAM_SCHEMA_REGISTRY_BASIC_AUTH_ENABLED`to true.
---
# 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.warpstream.com/warpstream/schema-registry/manage-security/basic-authentication.md?ask=&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.
