The uv auth CLI
uv provides a high-level interface for storing and retrieving credentials from services.
Logging in to a service
To add credentials for service, use the uv auth login command:
This will prompt for the credentials.
The credentials can also be provided using the --username and --password options, or the
--token option for services which use a __token__ or arbitrary username.
Note
We recommend providing the secret via stdin. Use - to indicate the value should be read from
stdin, e.g., for --password:
The same pattern can be used with --token.
Once credentials are added, uv will use them for packaging operations that require fetching content from the given service. At this time, only HTTPS Basic authentication is supported. The credentials will not yet be used for Git requests.
Note
The credentials will not be validated, i.e., incorrect credentials will not fail.
Logging out of a service
To remove credentials, use the uv auth logout command:
Note
The credentials will not be invalidated with the remote server, i.e., they will only be removed from local storage not rendered unusable.
Showing credentials for a service
To show the credential stored for a given URL, use the uv auth token command:
If a username was used to log in, it will need to be provided as well, e.g.:
Using credentials with external tools
uv auth helper allows tools that support credential helpers to request HTTP credentials from uv.
At this time, uv supports the
Bazel credential helper protocol.
The command is intended to be invoked by external tools. It reads a JSON request from stdin and
writes a JSON response to stdout. When matching credentials are available, the response includes the
Authorization header:
$ echo '{"uri": "https://example.com/path"}' | uv --preview-features auth-helper auth helper --protocol=bazel get
{"headers":{"Authorization":["Basic ..."]}}
If no credentials are found, uv will return an empty set of headers:
Note
uv auth helper is experimental. Use --preview-features auth-helper or
UV_PREVIEW_FEATURES=auth-helper to disable the warning.
The Bazel integration guide explains how to use this command with Bazel.
Configuring the storage backend
Credentials are persisted to the uv credentials store.
By default, credentials are written to a plaintext file. An encrypted system-native storage backend
can be enabled with UV_PREVIEW_FEATURES=native-auth.