---
title: influx v1 auth create
description: The influx v1 auth create command creates an authorization in the InfluxDB 1.x compatibility API.
url: https://docs.influxdata.com/influxdb/v2/reference/cli/influx/v1/auth/create/
estimated_tokens: 2116
product: InfluxDB OSS v2
version: v2
---

# influx v1 auth create

-   influx CLI 2.0.0+
-   InfluxDB 2.0.0+
-   Updated in CLI v2.0.3

This page documents an earlier version of InfluxDB OSS. [InfluxDB 3 Core](/influxdb3/core/) is the latest stable version.

#### API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — **capture any plaintext tokens you still need before you upgrade**.

For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing).

The `influx v1 auth create` command creates a legacy authorization with the [InfluxDB 1.x compatibility API](/influxdb/v2/reference/api/influxdb-1x/).

## Usage

```
influx v1 auth create [flags]
```

## Flags

| Flag |  | Description | Input type | Maps to ? |
| --- | --- | --- | --- | --- |
| -c | --active-config | Config name to use for command | string | INFLUX_ACTIVE_CONFIG |
|  | --configs-path | Path to the influx CLI configurations (default: ~/.influxdbv2/configs) | string | INFLUX_CONFIGS_PATH |
| -d | --description | Token description | string |  |
| -h | --help | Help for the create command |  |  |
|  | --hide-headers | Hide the table headers (default: false) |  | INFLUX_HIDE_HEADERS |
|  | --host | HTTP address of InfluxDB | string | INFLUX_HOST |
|  | --json | Output data as JSON (default: false) |  | INFLUX_OUTPUT_JSON |
|  | --no-password | Don’t prompt for a password (to use the token, you must set a password with influx v1 auth set-password) |  |  |
| -o | --org | Organization name (mutually exclusive with --org-id) | string | INFLUX_ORG |
|  | --org-id | Organization ID (mutually exclusive with --org) | string | INFLUX_ORG_ID |
|  | --password | Password to set on the authorization |  |  |
|  | --read-bucket | Bucket ID to assign read permissions to | stringArray |  |
|  | --skip-verify | Skip TLS certificate verification |  | INFLUX_SKIP_VERIFY |
| -t | --token | API token | string | INFLUX_TOKEN |
|  | --username | (Required) Token username | string |  |
|  | --write-bucket | Bucket ID to assign write permissions to | stringArray |  |

## Examples

#### Authentication credentials

The examples below assume your InfluxDB **host**, **organization**, and **token** are provided by either the [active `influx` CLI configuration](/influxdb/v2/reference/cli/influx/#provide-required-authentication-credentials) or by environment variables (`INFLUX_HOST`, `INFLUX_ORG`, and `INFLUX_TOKEN`). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

-   `--host`: [InfluxDB host](/influxdb/v2/reference/urls/)
-   `-o, --org` or `--org-id`: InfluxDB organization name or ID
-   `-t, --token`: InfluxDB API token

##### Create a v1 authorization with read and write permissions

```sh
# Create an authorization with read and write access to bucket 00xX00o0X001
# but only read access to bucket 00xX00o0X002
influx v1 auth create \
  --read-bucket 00xX00o0X001 \
  --read-bucket 00xX00o0X002 \
  --write-bucket 00xX00o0X001 \
  --username example-user
```

#### Related

-   [Upgrade from InfluxDB 1.x to 2.9](/influxdb/v2/install/upgrade/v1-to-v2/)
-   [influx CLI—Provide required authentication credentials](/influxdb/v2/reference/cli/influx/#provide-required-authentication-credentials)
-   [\`influx\` CLI—Flag patterns and conventions](/influxdb/v2/reference/cli/influx/#flag-patterns-and-conventions)

[authorization](/influxdb/v2/tags/authorization/)