Skip to content

Commit 5e9560d

Browse files
authored
Merge pull request #5790 from influxdata/jstirnaman/issue5781
Include the word `Bearer` or `Token`, a space, and your **token** value (all case-sensitive). Fix broken TOC links
2 parents f4c3332 + eb3ca6a commit 5e9560d

File tree

6 files changed

+14
-4
lines changed

6 files changed

+14
-4
lines changed

content/influxdb/v1/tools/api.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,7 @@ The `/api/v2/write` endpoint maps the supplied version 1.x database and retentio
141141
to access the platform and all its capabilities.
142142
InfluxDB v1.x uses a username and password combination when accessing the HTTP APIs.
143143
Use the Token schema to provide your InfluxDB 1.x username and password separated by a colon (`:`).
144+
The `Token` scheme is the word `Token`, a space, and your credentials (all case-sensitive).
144145
For example: `Authorization: Token username:password`.
145146

146147
{{< code-tabs-wrapper >}}

content/influxdb/v2/api-guide/influxdb-1x/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ Token authentication requires the following credential:
3636
- **token**: InfluxDB [API token](/influxdb/v2/admin/tokens/)
3737

3838
Use the `Authorization` header with the `Token` scheme to provide your token to InfluxDB.
39+
The `Token` scheme is the word `Token`, a space, and your token (all case-sensitive).
3940

4041
#### Syntax
4142

content/influxdb3/cloud-dedicated/guides/api-compatibility/v1/_index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ With the InfluxDB v1 API, you can use database tokens in InfluxDB 1.x username a
6868
schemes, in the InfluxDB v2 `Authorization: Token` scheme, or in the OAuth `Authorization: Bearer` scheme.
6969

7070
- [Authenticate with a username and password scheme](#authenticate-with-a-username-and-password-scheme)
71-
- [Authenticate with a token scheme](#authenticate-with-a-token)
71+
- [Authenticate with a token scheme](#authenticate-with-a-token-scheme)
7272

7373
### Authenticate with a username and password scheme
7474

@@ -158,6 +158,8 @@ The `Token` scheme is used in the InfluxDB 2.x API.
158158
`Bearer` is defined by the [OAuth 2.0 Framework](https://www.rfc-editor.org/rfc/rfc6750#page-14).
159159
Support for one or the other may vary across InfluxDB API clients.
160160

161+
Include the word `Bearer` or `Token`, a space, and your **token** value (all case-sensitive).
162+
161163
#### Syntax
162164

163165
```http

content/influxdb3/cloud-serverless/guides/api-compatibility/v1/_index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ With the InfluxDB v1 API, you can use API tokens in InfluxDB 1.x username and pa
5454
schemes or in the InfluxDB v2 `Authorization: Token` scheme.
5555

5656
- [Authenticate with a username and password scheme](#authenticate-with-a-username-and-password-scheme)
57-
- [Authenticate with a token scheme](#authenticate-with-a-token)
57+
- [Authenticate with a token scheme](#authenticate-with-a-token-scheme)
5858

5959
### Authenticate with a username and password scheme
6060

@@ -151,6 +151,8 @@ Replace the following:
151151
Use the `Authorization: Token` scheme to pass a [token](/influxdb3/cloud-serverless/admin/tokens/) for authenticating
152152
v1 API `/write` and `/query` requests.
153153

154+
Include the word `Token`, a space, and your **token** value (all case-sensitive).
155+
154156
#### Syntax
155157

156158
```http

content/influxdb3/clustered/get-started/write.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -450,7 +450,9 @@ Include the following with your request:
450450
With the {{% product-name %}}
451451
[v1 API `/write` endpoint](/influxdb3/clustered/api/#operation/PostLegacyWrite),
452452
`Authorization: Bearer` and `Authorization: Token` are equivalent and you can
453-
use either scheme to pass a database token in your request. For more information
453+
use either scheme to pass a database token in your request.
454+
Include the word `Bearer` or `Token`, a space, and your **token** value (all case-sensitive).
455+
For more information
454456
about HTTP API token schemes, see how to
455457
[authenticate API requests](/influxdb3/clustered/guides/api-compatibility/v1/).
456458
{{% /note %}}

content/influxdb3/clustered/guides/api-compatibility/v1/_index.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ With the InfluxDB v1 API, you can use database tokens in InfluxDB 1.x username a
6767
schemes, in the InfluxDB v2 `Authorization: Token` scheme, or in the OAuth `Authorization: Bearer` scheme.
6868

6969
- [Authenticate with a username and password scheme](#authenticate-with-a-username-and-password-scheme)
70-
- [Authenticate with a token scheme](#authenticate-with-a-token)
70+
- [Authenticate with a token scheme](#authenticate-with-a-token-scheme)
7171

7272
### Authenticate with a username and password scheme
7373

@@ -155,6 +155,8 @@ The `Token` scheme is used in the InfluxDB 2.x API.
155155
`Bearer` is defined by the [OAuth 2.0 Framework](https://www.rfc-editor.org/rfc/rfc6750#page-14).
156156
Support for one or the other may vary across InfluxDB API clients.
157157

158+
Include the word `Bearer` or `Token`, a space, and your **token** value (all case-sensitive).
159+
158160
#### Syntax
159161

160162
```http

0 commit comments

Comments
 (0)