mirror of
https://github.com/bitwarden/help
synced 2025-12-16 08:13:28 +00:00
committed by
GitHub
parent
e91b13b104
commit
b667eec297
@@ -76,9 +76,9 @@ bw login [email] [password] --method <method> --code <code>
|
|||||||
```
|
```
|
||||||
where `<method>` is your Two-step Login method (see [Enums](#enums)), and `<code>` is your Two-step Login code.
|
where `<method>` is your Two-step Login method (see [Enums](#enums)), and `<code>` is your Two-step Login code.
|
||||||
```
|
```
|
||||||
bw login --apiKey
|
bw login --apikey
|
||||||
```
|
```
|
||||||
where `--apiKey` will prompt you to enter your personal `client_id` and `client_secret`. For more information, see [Personal API Key for CLI Authentication](https://bitwarden.com/help/article/personal-api-key/).
|
where `--apikey` will prompt you to enter your personal `client_id` and `client_secret`. For more information, see [Personal API Key for CLI Authentication](https://bitwarden.com/help/article/personal-api-key/).
|
||||||
```
|
```
|
||||||
bw login --sso
|
bw login --sso
|
||||||
```
|
```
|
||||||
@@ -109,7 +109,7 @@ Pass the session key to CLI commands by setting the `BW_SESSION` environment var
|
|||||||
It is possible to persist your session key to your environment (for example, exporting it in `.bashrc`), however, we do not recommend doing this. Your active session key is the encryption key used to unlock all data associated with your Bitwarden vault and is not well-suited for persisting on an unprotected disk.
|
It is possible to persist your session key to your environment (for example, exporting it in `.bashrc`), however, we do not recommend doing this. Your active session key is the encryption key used to unlock all data associated with your Bitwarden vault and is not well-suited for persisting on an unprotected disk.
|
||||||
{% endcallout %}
|
{% endcallout %}
|
||||||
|
|
||||||
### `--apiKey` Variables
|
### `--apikey` Variables
|
||||||
|
|
||||||
The Bitwarden CLI will look for non-empty environment variables `BW_CLIENTID` or `BW_CLIENTSECRET`. Save these environment variables with your `client_id` and `client_secret` to prevent Bitwarden from prompting you every time.
|
The Bitwarden CLI will look for non-empty environment variables `BW_CLIENTID` or `BW_CLIENTSECRET`. Save these environment variables with your `client_id` and `client_secret` to prevent Bitwarden from prompting you every time.
|
||||||
|
|
||||||
|
|||||||
@@ -42,7 +42,7 @@ Rotating your key will invalidate your previous key and all active sessions usin
|
|||||||
|
|
||||||
To use your API Key to authenticate into the CLI, enter the following command:
|
To use your API Key to authenticate into the CLI, enter the following command:
|
||||||
```
|
```
|
||||||
bw login --apiKey
|
bw login --apikey
|
||||||
```
|
```
|
||||||
which will prompt you to enter the obtained `client_id` and `client_secret` to authenticate. Once you enter these values, enter your Master Password to decrypt your Vault. For more information, see [Bitwarden command line tool (CLI)](https://bitwarden.com/help/article/cli/).
|
which will prompt you to enter the obtained `client_id` and `client_secret` to authenticate. Once you enter these values, enter your Master Password to decrypt your Vault. For more information, see [Bitwarden command line tool (CLI)](https://bitwarden.com/help/article/cli/).
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user