DOC-781 | Access tokens (#743)

* WIP * WIP Access token examples * Complete API description, add release notes * [skip ci] Automatic commit of generated files from CircleCI

Author: Simran-B

site/content/3.12/components/tools/arangodb-shell/examples.md

@@ -15,7 +15,7 @@ command-line options:
 - `--server.database <string>`: name of the database to connect to
 - `--server.endpoint <string>`: endpoint to connect to
 - `--server.username <string>`: database username
-- `--server.password <string>`: password to use when connecting 
+- `--server.password <string>`: password or access token to use when connecting 
 - `--server.authentication <bool>`: whether or not to use authentication
 
 For example, to connect to an ArangoDB server on IP `192.168.173.13` on port
@@ -26,7 +26,9 @@ arangosh --server.endpoint tcp://192.168.173.13:8530 --server.username foo --ser
 ```
 
 _arangosh_ then displays a password prompt and tries to connect to the 
-server after the password is entered.
+server after the password is entered. You can also use an access token instead
+of a password (but make sure `--server.username` is set to the same user name as
+encoded in the access token).
 
 {{< warning >}}
 At signs `@` in startup option arguments need to be escaped as `@@`.

site/content/3.12/components/tools/arangodump/examples.md

@@ -27,8 +27,8 @@ following startup options:
 
 - `--server.endpoint <string>`: endpoint to connect to
 - `--server.username <string>`: username
-- `--server.password <string>`: password to use (omit this and you'll be prompted for the
- password)
+- `--server.password <string>`: password or access token to use
+ (omit this and you'll be prompted for the password)
 - `--server.authentication <bool>`: whether or not to use authentication
 
 If you want to connect to a different database or dump all databases you can additionally

site/content/3.12/components/tools/arangoexport/examples.md

@@ -25,8 +25,8 @@ or use authentication, you can use the following command-line options:
 - `--server.database <string>`: the name of the database to connect to
 - `--server.endpoint <string>`: the endpoint to connect to
 - `--server.username <string>`: the username
-- `--server.password <string>`: the password to use (omit this to get prompted
- for the password)
+- `--server.password <string>`: password or access token to use
+ (omit this and you'll be prompted for the password)
 - `--server.authentication <bool>`: whether or not to use authentication
 
 Here is an example of exporting data from a non-standard endpoint, using a dedicated

site/content/3.12/components/tools/arangoimport/examples-json.md

@@ -209,7 +209,7 @@ By default, the endpoint `tcp://127.0.0.1:8529` is used. If you want to
 specify a different endpoint, you can use the `--server.endpoint` option. You
 probably want to specify a database user and password as well. You can do so by
 using the options `--server.username` and `--server.password`. If you do not
-specify a password, you are prompted for one.
+specify a password (or access token), you are prompted for one.
 
 ```
 arangoimport --server.endpoint tcp://127.0.0.1:8529 --server.username root ...

site/content/3.12/components/tools/arangoinspect/examples.md

@@ -31,7 +31,7 @@ arangoinspect --server.endpoint tcp://127.0.0.1:8529
 This starts the tool with a prompt for the JWT secret and tries to connect
 to the specified ArangoDB server. You have to type the secret as is used for
 the `arangod` option `--server.jwt-secret`. For non-cluster deployments,
-you may authenticate with a user name and password instead:
+you may authenticate with a user name and password (or access token) instead:
 
 ```
 arangoinspect --server.ask-jwt-secret false --server.username "root" --server.password "foobar"

site/content/3.12/components/tools/arangorestore/examples.md

@@ -25,7 +25,7 @@ following startup options:
 
 - `--server.endpoint <string>`: endpoint to connect to
 - `--server.username <string>`: username
-- `--server.password <string>`: password to use
+- `--server.password <string>`: password or access token to use
  (omit this and you'll be prompted for the password)
 - `--server.authentication <bool>`: whether or not to use authentication