> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/unable-to-authenticate-with-openstack-cli.md).

# Unable to Authenticate With OpenStack CLI

## Problem

* Using the same credentials which successfully authenticate a user in the Clarity UI, running OpenStack CLI commands after sourcing the credentials file fails with the following error:

{% tabs %}
{% tab title="Sample" %}

```bash
$ openstack server list
The request you have made requires authentication. (HTTP 401) (Request-ID: req-b4861fe6-0ad5-47ae-b321-d0aad26ff18b)
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* OpenStack CLI (unified or project specific)

## Cause

Special characters in the **OS\_PASSWORD** environment variable set using the instruction available in the Platform9 document, [Installing OpenStack CLI Clients](https://docs.platform9.com/support/getting-started-with-the-openstack-command-line/), must be 'escaped' to prevent the shell from interpreting them in an unintended manner.

## Resolution

1. List the OpenStack environment variables, and note any which do not return exactly as intended.

{% tabs %}
{% tab title="Command" %}

```none
$ env | grep OS_
```

{% endtab %}
{% endtabs %}

2. Identify the first character for each variable which is not returned in the output of the command in Step #1 and insert a backslash () into the variable's value just before the identified character.
3. Source the edited *rc* file.

{% tabs %}
{% tab title="Command" %}

```none
$ . openstack.rc
```

{% endtab %}
{% endtabs %}

4. Verify commands are now returning expected output as would be seen in the UI using the installed OpenStack CLI.


---

# 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 dynamically by asking a question.

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

```
GET https://platform9.com/kb/pmo/solution/unable-to-authenticate-with-openstack-cli.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 `build a script that syncs our docs to a CMS` 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.