Zenoh

https://zenoh.io/docs
Admin
Zenoh is a zero overhead pub/sub/query protocol that unifies data in motion, data at rest, and...
Tokens:33,082
Snippets:262
Trust Score:8.6
Update:2 weeks ago
Show doc for...
Tokens:
Raw
### Start the subscriber

Source: https://zenoh.io/docs/getting-started/first-app

Start the subscriber application. It waits for updates on 'myhome/kitchen/temp'.

```bash
python3 z_subscriber.py

```

--------------------------------

### Install Zenoh with apt

Source: https://zenoh.io/docs/getting-started/installation

Installs the Zenoh router on Debian/Ubuntu using apt.

```bash
$ sudo apt install zenoh

```

--------------------------------

### Start the Zenoh router on macOS

Source: https://zenoh.io/docs/getting-started/installation

Starts the Zenoh router on macOS after installation.

```bash
$ zenohd

```

--------------------------------

### Start Zenoh router with configuration

Source: https://zenoh.io/docs/getting-started/first-app

Start the Zenoh router (zenohd) with the provided configuration file to enable storage.

```bash
zenohd -c zenoh-myhome.json5

```

--------------------------------

### Start the sensor publisher

Source: https://zenoh.io/docs/getting-started/first-app

Start the sensor publisher application. The subscriber will then receive and print the temperature values.

```bash
python3 z_sensor.py

```

--------------------------------

### Start the Zenoh router on Windows

Source: https://zenoh.io/docs/getting-started/installation

Navigates to the Zenoh directory and starts the Zenoh router on Windows.

```powershell
> cd C:\path\to\zenoh\dir
> zenohd.exe

```

--------------------------------

### Install the zenoh Python library

Source: https://zenoh.io/docs/getting-started/first-app

Install the zenoh Python library using pip. This is the first step before writing any Zenoh application.

```bash
pip install eclipse-zenoh

```

--------------------------------

### Install Zenoh with Homebrew

Source: https://zenoh.io/docs/getting-started/installation

Installs the Zenoh router (zenohd) on macOS using Homebrew.

```bash
$ brew install zenoh

```

--------------------------------

### Full ACL configuration example

Source: https://zenoh.io/docs/manual/access-control

Complete example configuration for Zenoh 1.0 access control, showing the access_control object with enabled, default_permission, rules, subjects, and policies. The rule denies pub/sub messages on demo/example/** for ingress and egress flows. The subject matches interfaces, cert common names, and usernames. The policy binds the rule to the subject.

```json
{
  "access_control": {
    "enabled": true,
    "default_permission": "allow",
  
    "rules": [
      {
        "id": "deny pub/sub",
        "permission": "deny",
        "flows": ["ingress", "egress"],
        "messages": [
          "declare_subscriber",
          "put",
          "delete",
        ],
        "key_exprs": [
          "demo/example/**",
        ],
      }
    ],
  
    "subjects": [
      {
        "id": "example subject",
        "interfaces": [
          "lo0",
          "en0",
        ],
        "cert_common_names": [
          "example.zenoh.io"
        ],
        "usernames": [
          "zenoh-example1",
          "zenoh-example2",
        ],
      }
    ],
  
    "policies": [
      {
        "rules": [
          "deny pub/sub"
        ],
        "subjects": [
          "example subject"
        ],
      },
    ]
  }
}
```

--------------------------------

### Test Zenoh Installation with zenohd --help

Source: https://zenoh.io/docs/getting-started/installation

Run `zenohd --help` to display the Zenoh router's help text, which lists all command-line options and their descriptions. The output shows the version, usage, and options such as `--config`, `--listen`, `--connect`, `--plugin`, and `--cfg`.

```bash
$ zenohd --help

```

```text
2024-08-12T13:27:29.724708Z  INFO main ThreadId(01) zenohd: zenohd v0.11.0-dev-965-g764be602d built with rustc 1.75.0 (82e1608df 2023-12-21)
The zenoh router

Usage: zenohd [OPTIONS]

Options:
  -c, --config <PATH>
          The configuration file. Currently, this file must be a valid JSON5 or YAML file

  -l, --listen <ENDPOINT>
          Locators on which this router will listen for incoming sessions. Repeat this option to open several listeners

  -e, --connect <ENDPOINT>
          A peer locator this router will try to connect to. Repeat this option to connect to several peers

  -i, --id <ID>
          The identifier (as an hexadecimal string, with odd number of chars - e.g.: A0B23...) that zenohd must use. If not set, a random unsigned 128bit integer will be used. WARNING: this identifier must be unique in the system and must be 16 bytes maximum (32 chars)!

  -P, --plugin <PLUGIN>
          A plugin that MUST be loaded. You can give just the name of the plugin, zenohd will search for a library named 'libzenoh_plugin_\<name\>.so' (exact name depending the OS). Or you can give such a string: "\<plugin_name\>:\<library_path\>" Repeat this option to load several plugins. If loading failed, zenohd will exit

      --plugin-search-dir <PATH>
          Directory where to search for plugins libraries to load. Repeat this option to specify several search directories

      --no-timestamp
          By default zenohd adds a HLC-generated Timestamp to each routed Data if there isn't already one. This option disables this feature

      --no-multicast-scouting
          By default zenohd replies to multicast scouting messages for being discovered by peers and clients. This option disables this feature

      --rest-http-port <SOCKET>
          Configures HTTP interface for the REST API (enabled by default on port 8000). Accepted values: - a port number - a string with format `<local_ip>:<port_number>` (to bind the HTTP server to a specific interface) - `none` to disable the REST API

      --cfg <CFG>
          Allows arbitrary configuration changes as column-separated KEY:VALUE pairs, where: - KEY must be a valid config path. - VALUE must be a valid JSON5 string that can be deserialized to the expected type for the KEY field.
          
          Examples: - `--cfg='startup/subscribe:["demo/**"]'` - `--cfg='plugins/storage_manager/storages/demo:{key_expr:"demo/example/**",volume:"memory"}'`

      --adminspace-permissions <[r|w|rw|none]>
          Configure the read and/or write permissions on the admin space. Default is read only

  -h, --help
          Print help (see a summary with '-h')

  -V, --version
          Print version

```

--------------------------------

### Rule example: deny pub/sub

Source: https://zenoh.io/docs/manual/access-control

A single rule configuration that denies all incoming and outgoing subscriptions, publications, and deletions on key expressions matching demo/example/**. This rule is used as an example in the rules section.

```json
{
  "id": "deny pub/sub",
  "permission": "deny",
  "flows": ["ingress", "egress"],
  "messages": [
    "declare_subscriber",
    "put",
    "delete",
  ],
  "key_exprs": [
    "demo/example/**",
  ],
}
```

--------------------------------

### Subject configuration with interfaces, cert_common_names, and usernames

Source: https://zenoh.io/docs/manual/access-control

Example subject configuration showing the Cartesian product of interfaces, cert_common_names, and usernames. The comment shows the internal filter representation.

```json
{
  "id": "example subject",
  "interfaces": [
    "lo0",
    "en0",
  ],
  "cert_common_names": [
    "example.zenoh.io"
  ],
  "usernames": [
    "zenoh-example1",
    "zenoh-example2",
  ],
  // This instance translates internally to this filter:
  // (interface="lo0" AND cert_common_name="example.zenoh.io" AND username="zenoh-example1") OR
  // (interface="lo0" AND cert_common_name="example.zenoh.io" AND username="zenoh-example2") OR
  // (interface="en0" AND cert_common_name="example.zenoh.io" AND username="zenoh-example1") OR
  // (interface="en0" AND cert_common_name="example.zenoh.io" AND username="zenoh-example2")
}
```

--------------------------------

### Run Zenoh peers over QUIC

Source: https://zenoh.io/docs/manual/quic

Commands to start two Zenoh peers in peer-to-peer mode over QUIC. The first peer listens on quic/localhost:7447, and the second peer listens on quic/localhost:7448 and connects to the first peer via -e quic/localhost:7447. Both use the same peer.json5 configuration file.

```bash
$ z_sub -c peer.json5 -l quic/localhost:7447

```

```bash
$ z_pub -c peer.json5 -l quic/localhost:7448 -e quic/localhost:7447

```

--------------------------------

### Run Zenoh peers with TLS

Source: https://zenoh.io/docs/manual/tls

Commands to start two peers in peer mode using the same peer.json5 configuration. The first peer listens on tls/localhost:7447, and the second peer listens on tls/localhost:7448 and connects to the first peer.

```bash
$ z_sub -c peer.json5 -l tls/localhost:7447

```

```bash
$ z_pub -c peer.json5 -l tls/localhost:7448 -e tls/localhost:7447

```

--------------------------------

### HTTP PUT request with curl and fetch

Source: https://zenoh.io/docs/manual/plugin-storage-manager

Shows the equivalent HTTP PUT request using curl and JavaScript's fetch. The curl example includes inline comments explaining each part of the command.

```bash
curl -X PUT        'http://hostname:8000/key/expression' -H 'content-type:application/json'      -d '{"some": ["json", "data"]}'
#    ^HTTP METHOD  ^Target URL for the request           ^Header saying the data is in JSON      ^The body of the request
```

```javascript
fetch('http://hostname:8000/key/expression', {
      method: 'PUT',
      headers: {'Content-Type': 'application/json'},
      body: JSON.stringify({some: ["json", "data"]})
    })
```

--------------------------------

### Peer TLS configuration (peer.json5)

Source: https://zenoh.io/docs/manual/tls

Configuration for a Zenoh peer to enable TLS. Requires 'root_ca_certificate', 'listen_private_key', and 'listen_certificate'. The peer uses the root CA to authenticate the TLS certificate of the peer it connects to, and uses the key and certificate for incoming TLS sessions. This example is saved as 'peer.json5'.

```json
{
  /// The node's mode (router, peer or client)
  "mode": "peer",
  "transport": {
    "link": {
      "tls": {
        "root_ca_certificate": "/home/user/tls/minica.pem",
        "listen_private_key": "/home/user/tls/localhost/key.pem",
        "listen_certificate": "/home/user/tls/localhost/cert.pem"
      }
    }
  }
}
```

--------------------------------

### Listener configuration for close_link_on_expiration

Source: https://zenoh.io/docs/manual/tls

Example Zenoh config for a router acting as TLS server with certificate expiration monitoring. Requires 'enable_mtls' to be true for the listener to monitor certificate expiration.

```json
{
  "mode": "router",
  "listen": {
    "endpoints": ["tls/localhost:7447"]
  },
  "transport": {
    "link": {
      "tls": {
        "root_ca_certificate": "/home/user/client/minica.pem",
        "listen_private_key": "/home/user/server/localhost/key.pem",
        "listen_certificate": "/home/user/server/localhost/cert.pem",
        "enable_mtls": true,
        "close_link_on_expiration": true
      }
    }
  }
}
```

--------------------------------

### Router TLS configuration (server.json5)

Source: https://zenoh.io/docs/manual/tls

Configuration for a Zenoh router to enable TLS. Requires 'listen_private_key' and 'listen_certificate' fields. The router uses these to establish TLS sessions with clients. This example is saved as 'server.json5'.

```json
{
  /// The node's mode (router, peer or client)
  "mode": "router",
  "listen": {
    "endpoints": ["tls/localhost:7447"]
  },
  "transport": {
    "link": {
      "tls": {
        "listen_private_key": "/home/user/tls/localhost/key.pem",
        "listen_certificate": "/home/user/tls/localhost/cert.pem"
      }
    }
  }
}
```

--------------------------------

### Tap the Eclipse Zenoh Homebrew repository

Source: https://zenoh.io/docs/getting-started/installation

Adds the Eclipse Zenoh Homebrew tap so the zenoh package can be installed on macOS.

```bash
$ brew tap eclipse-zenoh/homebrew-zenoh

```

--------------------------------

### Get storages via REST API

Source: https://zenoh.io/docs/getting-started/quick-test

Retrieves the storages of the local router, which should return the demo storage that was just created.

```bash
curl 'http://localhost:8000/@/local/router/status/plugins/storage_manager/storages/*'
```

--------------------------------

### GET keys/values via curl

Source: https://zenoh.io/docs/apis/rest

Use the GET operation to retrieve keys/values matching a selector. The response is a JSON array of objects with "key", "value", "encoding", and "time". The third example uses -g to disable globbing for the admin space selector.

```bash
# Get the keys/values matching demo/**
$ curl http://localhost:8000/demo/**
[
{ "key": "demo/example/zenoh-python-put",
  "value": "Put from Python!",
  "encoding": "text/plain",
  "time": "2022-03-29T10:19:38.988830998Z/BC99B84DD73D449FB7B5C03506934604" },
{ "key": "demo/example/zenoh-c-put",
  "value": "Put from Python!",
  "encoding": "text/plain",
  "time": "2022-03-29T10:19:40.031682968Z/BC99B84DD73D449FB7B5C03506934604" },
{ "key": "demo/example/zenoh-rs-put",
  "value": "Put from Python!",
  "encoding": "text/plain",
  "time": "2022-03-29T10:19:45.879540920Z/BC99B84DD73D449FB7B5C03506934604" },
]

# Get the keys/values matching demo/example/*eval (i.e. the Zenoh eval examples)
# with property name=Bob
$ curl http://localhost:8000/demo/example/*eval?(name=Bob)
[
{ "key": "demo/example/zenoh-rs-eval",
  "value": "Eval from Bob",
  "encoding": "text/plain",
  "time": "None" }
]

# Get the list of storages via a Get on admin space (@/...)
$ curl -g http://localhost:8000/@/**/storages/**
[
{ "key": "@/router/BC99B84DD73D449FB7B5C03506934604/status/plugins/storage_manager/storages/demo",
  "value": {"key_expr":"demo/example/**","volume":"memory"},
  "encoding": "application/json",
  "time": "None" }
]

```

--------------------------------

### PUT values via curl

Source: https://zenoh.io/docs/apis/rest

Use the PUT operation to write values to a key expression. The content-type header determines the Zenoh Value type; for example, text/plain becomes TextPlain and application/json becomes AppJson. The third example creates a memory storage via the admin space.

```bash
# Put a string value in demo/example/test
curl -X PUT -H "content-type:text/plain" -d 'Hello World!' http://localhost:8000/demo/example/test

# Put a JSON value in demo/example/json
curl -X PUT -H "content-type:application/json" -d '{"value": "Hello World!"}' http://localhost:8000/demo/example/test

# Create a Memory storage on demo/test/** via a Put on admin space (@/...)
curl -X PUT -H 'content-type:application/json' http://localhost:8000/@/local/router/config/plugins/storage_manager/storages/demo -d '{key_expr:"demo/test/**", volume:"memory"}' 

```

--------------------------------

### GET /<selector>

Source: https://zenoh.io/docs/apis/rest

Retrieves keys and values matching a Zenoh selector via the REST API.

```APIDOC
## GET /<selector>

### Description
Binds to the **get(selector)** operation on Zenoh. Retrieves keys and values matching the given selector.

### Method
GET

### Endpoint
`http://host:8000/<selector>`

### Parameters
#### Path Parameters
- **selector** (string) - Required - The Zenoh selector to query.

#### Query Parameters
- **name** (string) - Optional - Property to pass to eval operations (e.g., `name=Bob`).

### Request Example
```
curl http://localhost:8000/demo/**
```

### Response
#### Success Response (200)
Returns a JSON array of objects with fields:
- **key** (string) - The key of the value.
- **value** (string) - The value.
- **encoding** (string) - The encoding of the value.
- **time** (string) - The timestamp of the value.

#### Response Example
```json
[
  { "key": "demo/example/zenoh-python-put", "value": "Put from Python!", "encoding": "text/plain", "time": "2022-03-29T10:19:38.988830998Z/BC99B84DD73D449FB7B5C03506934604" }
]
```
```

--------------------------------

### GET /<key_expression> (SSE)

Source: https://zenoh.io/docs/apis/rest

Establishes a long-lived SSE connection to receive samples matching a key expression.

```APIDOC
## GET /<key_expression> (SSE)

### Description
Binds to the **declare_subscriber(key_expression)** operation on Zenoh. Establishes a long-lived SSE connection to receive samples matching the key expression.

### Method
GET

### Endpoint
`http://host:8000/<key_expression>`

### Parameters
#### Path Parameters
- **key_expression** (string) - Required - The key expression to subscribe to.

#### Headers
- **Accept** (string) - Required - Must be `text/event-stream` to upgrade to SSE.

### Response
#### Success Response (200)
The connection is upgraded to SSE, and Zenoh forwards matching samples in JSON format.
```

--------------------------------

### Run Zenoh router and clients over QUIC

Source: https://zenoh.io/docs/manual/quic

Commands to run a Zenoh router and two clients (subscriber and publisher) in client-router mode over QUIC. The router uses router.json5, and both clients use the same client.json5 configuration file.

```bash
$ zenohd -c router.json5

```

```bash
$ z_sub -c client.json5

```

```bash
$ z_pub -c client.json5

```

--------------------------------

### Run Zenoh router with plugins/backends volume

Source: https://zenoh.io/docs/getting-started/quick-test

Runs the Zenoh router in Docker while mounting a local directory as a volume to /root/.zenoh, allowing the router to find plugins and backends libraries. The libraries must be compiled for the x86_64-unknown-linux-musl target.

```bash
docker run --init -p 7447:7447/tcp -p 8000:8000/tcp -v $(pwd)/zenoh-docker:/root/.zenoh eclipse/zenoh
```

--------------------------------

### Get key/value via REST API

Source: https://zenoh.io/docs/getting-started/quick-test

Retrieves the value associated with the key demo/example/test via the REST API.

```bash
curl http://localhost:8000/demo/example/test
```

--------------------------------

### Get local router info via REST API

Source: https://zenoh.io/docs/getting-started/quick-test

Retrieves information about the local Zenoh router via the REST API.

```bash
curl http://localhost:8000/@/local/router
```

--------------------------------

### Create z_sensor.py publisher

Source: https://zenoh.io/docs/getting-started/first-app

A publisher application that produces random temperature readings (15-30) every second on the key 'myhome/kitchen/temp'. It opens a Zenoh session, declares a publisher, and puts string values in a loop.

```python
import zenoh, random, time

random.seed()

def read_temp():
    return random.randint(15, 30)

if __name__ == "__main__":
    with zenoh.open(zenoh.Config()) as session:
        key = 'myhome/kitchen/temp'
        pub = session.declare_publisher(key)
        while True:
            t = read_temp()
            buf = f"{t}"
            print(f"Putting Data ('{key}': '{buf}')...")
            pub.put(buf)
            time.sleep(1)

```

--------------------------------

### Generate TLS certificates with minica for localhost

Source: https://zenoh.io/docs/manual/tls

Commands to create a directory, generate a TLS certificate for localhost using minica, and list the resulting files. The output shows the created files: minica.pem (root CA), and inside the localhost folder, cert.pem and key.pem.

```bash
$/home/user: mkdir tls
$/home/user: cd tls
$/home/user/tls: pwd
/home/user/tls

```

```bash
$/home/user/tls: minica --domains localhost

```

```bash
$/home/user/tls: ls
localhost   minica-key.pem  minica.pem

```

```bash
$/home/user/tls: ls localhost
cert.pem    key.pem

```

--------------------------------

### Policy associating rule with subject

Source: https://zenoh.io/docs/manual/access-control

Policy object that applies the 'deny pub/sub' rule to the 'example subject' subject. Lists allow multiple rules and subjects in one policy.

```json
{
  "rules": [
    "deny pub/sub"
  ],
  "subjects": [
    "example subject"
  ],
}
```

--------------------------------

### Create z_subscriber.py subscriber

Source: https://zenoh.io/docs/getting-started/first-app

A subscriber application that listens for updates on 'myhome/kitchen/temp' and prints each received sample. It runs for 60 seconds.

```python
import zenoh, time

def listener(sample):
    print(f"Received {sample.kind} ('{sample.key_expr}': '{sample.payload.to_string()}') ")

if __name__ == "__main__":
    with zenoh.open(zenoh.Config()) as session:
        sub = session.declare_subscriber('myhome/kitchen/temp', listener)
        time.sleep(60)

```

--------------------------------

### Client configuration for close_link_on_expiration

Source: https://zenoh.io/docs/manual/tls

Example Zenoh config for a TLS client with certificate expiration monitoring. Set 'close_link_on_expiration' to true to enable the feature. mTLS-related fields can be added if required.

```json
{
  "mode": "client",
  "connect": {
    "endpoints": ["tls/localhost:7447"]
  },
  "transport": {
    "link": {
      "tls": {
        "root_ca_certificate": "/home/user/server/minica.pem",
        "close_link_on_expiration": true
      }
    }
  }
}
```

--------------------------------

### Router/peer configuration with dictionary_file and credentials file

Source: https://zenoh.io/docs/manual/user-password

Router/peer configuration and the authorized credentials file. The dictionary_file points to a text file with authorized credentials in user:password format, one per line. The router uses its own credentials for outgoing authentication and the file for incoming connections.

```json5
{
  /// The node's mode (router, peer or client)
  mode: "router",
  transport: {
    auth: {
      /// The configuration of authentication.
      usrpwd: {
        user: "routerusername",
        password: "routerpassword",
        /// The path to a file containing the user password dictionary
        dictionary_file: "credentials.txt",
      },
    },
  },
}

```

```text
clientusername:clientpassword

```

--------------------------------

### DELETE values via curl

Source: https://zenoh.io/docs/apis/rest

Use the DELETE operation to remove a value or a storage. The first example removes a value by key; the second removes a storage via the admin space.

```bash
# Remove the value with key demo/example/test
curl -X DELETE http://localhost:8000/demo/example/test

# Remove a storage via a Remove on admin space (@/...)
curl -X DELETE http://localhost:8000/@/local/router/config/plugins/storage_manager/storages/demo

```

--------------------------------

### Create zenoh-myhome.json5 configuration

Source: https://zenoh.io/docs/getting-started/first-app

Configuration file for the Zenoh router to enable the REST plugin on port 8000 and configure a storage named 'myhome' that stores data for keys matching 'myhome/**' using the memory volume.

```json5
{
  plugins: {
    rest: {                        // activate and configure the REST plugin
      http_port: 8000              // with HTTP server listening on port 8000
    },
    storage_manager: {             // activate and configure the storage_manager plugin
      storages: {
        myhome: {                  // configure a "myhome" storage
          key_expr: "myhome/**",   // which subscribes and replies to query on myhome/**
          volume: {                // and using the "memory" volume (always present by default)
            id: "memory"
          }
        }
      }
    }
  }
}

```

--------------------------------

### File structure for mTLS keys and certificates

Source: https://zenoh.io/docs/manual/tls

Directory structure for storing the two sets of keys and certificates (server and client) under `$home/user/`. The appendix explains how to generate them.

```text
user
├── client
│   ├── localhost
│   │   ├── cert.pem
│   │   └── key.pem
│   ├── minica-key.pem
│   └── minica.pem
└── server
    ├── localhost
    │   ├── cert.pem
    │   └── key.pem
    ├── minica-key.pem
    └── minica.pem

```

--------------------------------

### Enable multistream QUIC with multistream=1

Source: https://zenoh.io/docs/manual/quic

Enables multistream QUIC by adding multistream=1 to the endpoint parameters. This maps each Zenoh priority level to a dedicated QUIC stream, preventing head-of-line blocking. If not provided, the default is auto, which negotiates usage via QUIC ALPN and maintains compatibility with older Zenoh versions.

```json
{
  "connect": {
    "endpoints": ["quic/localhost:7447?multistream=1"]
  },
}

```

--------------------------------

### Add a storage with memory volume

Source: https://zenoh.io/docs/manual/plugin-storage-manager

Adds a storage named 'my-storage' using the integrated 'memory' volume, which requires no extra configuration. The storage works on the key expression 'demo/my-storage/**'.

```bash
curl -X PUT 'http://hostname:8000/@/local/router/config/plugins/storage_manager/storages/my-storage' -H 'content-type:application/json' -d '{"key_expr": "demo/my-storage/**", "volume": "memory"}'
```

--------------------------------

### Hashed client and router configurations with credentials file

Source: https://zenoh.io/docs/manual/user-password

Updated client and router configurations and credentials file after hashing the passwords. The password fields now contain the SHA-256 hashes instead of clear text. The credentials file uses the hashed client password.

```json5
{
  /// The node's mode (router, peer or client)
  mode: "client",
  transport: {
    auth: {
      /// The configuration of authentication.
      /// A password implies a username is required.
      usrpwd: {
        user: "clientusername",
        password: "92df0d4f39c218607e3200bf93ccac87a80cb910e811d84b286bebe0a8860724",
      },
    },
  },
}

```

```json5
{
  /// The node's mode (router, peer or client)
  mode: "router",
  transport: {
    auth: {
      /// The configuration of authentication.
      usrpwd: {
        user: "routerusername",
        password: "2ce01a11893f276a4064f586f24b8f1868008e2e623f6c4e74ef381247e49df1",
        /// The path to a file containing the user password dictionary
        dictionary_file: "credentials.txt",
      },
    },
  },
}

```

```text
clientusername:92df0d4f39c218607e3200bf93ccac87a80cb910e811d84b286bebe0a8860724

```
Tokens:
Raw