aspera-cli 4.24.1 → 4.25.0.pre

data/README.md

@@ -2,7 +2,7 @@
 <!--
 DO NOT EDIT: THIS FILE IS GENERATED, edit docs/README.erb.md, for details, read docs/README.md
 PANDOC_META_BEGIN
-subtitle: "ascli 4.24.1"
+subtitle: "ascli 4.25.0.pre"
 author: "Laurent MARTIN"
 PANDOC_META_END
 -->
@@ -10,26 +10,27 @@ PANDOC_META_END
 
 <!-- NOTE CAUTION WARNING IMPORTANT TIP INFO -->
 
+<!-- markdownlint-disable MD028 -->
+
 [![Gem Version](https://badge.fury.io/rb/aspera-cli.svg)](https://badge.fury.io/rb/aspera-cli)
 [![unit tests](https://github.com/IBM/aspera-cli/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/IBM/aspera-cli/actions)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/5861/badge)](https://bestpractices.coreinfrastructure.org/projects/5861)
 
 ## Introduction
 
-![Hootput the Owl](docs/ascli-impersonation-small.png)
+![Hootput the Owl](docs/ascli-impersonation.svg)
 
 Hootput lives in the terminal, watching over every command with wide, unblinking eyes.
 Known for concise output and sharp insight, this owl thrives where others get lost in the dark.
 It doesn’t chatter; it hoots—clear, precise, and always on time.
 
-Like ascli, Hootput is built for action: launching transfers, parsing options, and navigating APIs without hesitation.
+Like `ascli`, Hootput is built for action: launching transfers, parsing options, and navigating APIs without hesitation.
 Light on feathers but heavy on wisdom, it turns complexity into simple one-liners.
 When you hear Hootput’s call, you know your data is already in flight.
 
 ---
 
-
-"Hey, I’m ascli — your data’s personal courier.
+"Hey, I’m `ascli` — your data’s personal courier.
 I don’t do flashy dashboards; I’m happiest in a terminal window.
 Hand me a command, and I’ll zip your files across the network faster than you thought possible.
 
@@ -41,9 +42,9 @@ Need to debug? I’ll show you what’s going on under the hood.
 
 Think of me as Aspera’s command-line sidekick: quick, reliable, and a little no-nonsense. You bring the files; I’ll bring the horsepower."
 
-Version : 4.24.1
+Version : 4.25.0.pre
 
-Laurent/2016-2025
+Laurent/2016-2026
 
 The aspera-cli Ruby gem offers a powerful command-line interface (CLI, `ascli`) for IBM Aspera software, facilitating seamless interaction with Aspera APIs and enabling high-performance file transfers.
 It also serves as an excellent resource for developers seeking to explore and understand the Aspera API ecosystem.
@@ -62,7 +63,7 @@ Minimum required Ruby version: >= 3.1.
 
 Release notes: see [CHANGELOG.md](CHANGELOG.md)
 
-A PDF version of this documentation is available here: [docs/Manual.pdf](docs/Manual.pdf).
+A PDF version of this documentation is delivered with [releases](https://github.com/IBM/aspera-cli/releases).
 
 ### BUGS, FEATURES, CONTRIBUTION
 
@@ -105,9 +106,10 @@ While `ascp` can be used directly, it is limited to basic send/receive operation
 
 ### Notations, Shell, Examples
 
-Command line operations examples are shown using a shell such as: `bash` or `zsh`.
+Command line operations examples are shown using a shell such as: `bash` (Linux) or `zsh` (macOS).
+Using [Windows PowerShell or cmd](#shell-parsing-for-windows) is also possible.
 
-Command line arguments beginning with `my_` in examples, e.g. `my_param_value`, are user-provided value and not fixed value commands.
+Command line arguments beginning with `my_` in examples, e.g. `my_param_value`, are user-provided value, and not fixed value commands.
 
 `ascli` is an API **Client** toward the remote Aspera application **Server** (Faspex, HSTS, etc...)
 
@@ -116,7 +118,7 @@ The transfer is not directly implemented in `ascli`, rather `ascli` uses one of
 
 > [!NOTE]
 > A **[Transfer Agent](#transfer-clients-agents)** is a client for the remote Transfer Server (HSTS/HSTE).
-> It can be local or remote.
+> It can be local, or remote.
 > For example a remote Aspera Transfer Server may be used as a transfer agent (using Node API).
 > i.e. using option `--transfer=node`
 
@@ -133,7 +135,7 @@ ascli --version
 ```
 
 ```text
-4.24.1
+4.25.0.pre
 ```
 
 > [!NOTE]
@@ -143,7 +145,7 @@ ascli --version
 
 Once installation is completed, you can proceed to the first use with a demo server:
 
-If you want to test with Aspera on Cloud, jump to section: [Wizard](#configuration-using-wizard).
+If you want to test with Aspera on Cloud, jump to section: [Wizard](#wizard).
 
 To test with Aspera demo transfer server, set up the environment and then test:
 
@@ -246,16 +248,31 @@ If you don't have internet for the installation, refer to section [Installation
 
 ### Single file executable
 
-It is planned to provide `ascli` as a single platform-dependent executable.
-[Beta releases can be found here](https://ibm.biz/aspera-cli-exe).
-
 > [!CAUTION]
 > This is a Beta feature.
-> On Linux, the executable requires a minimum GLIBC version.
+
+`ascli` is available as a single **platform-dependent executable**.
+[Beta releases can be found here](https://ibm.biz/aspera-cli-exe).
+
+Installation:
+
+```shell
+curl -o ascli https://eudemo.asperademo.com/download/aspera-cli/ascli.4.24.1.osx-arm64
+chmod a+x ascli
+./ascli conf transferd install
+```
+
+> [!NOTE]
+> Replace the URL with the one for your platform.
 > Installation of `ascp` is still required separately.
 > Refer to [Install `ascp`](#installation-of-ascp-through-transferd).
->
-> On Linux, check the minimum required GLIBC on this site: [repology.org](https://repology.org/project/glibc/versions), or check your GLIBC version with `ldd`:
+
+#### Linux: GLIBC version
+
+> [!CAUTION]
+> On Linux, the executable requires a minimum GLIBC version, specified in the executable name on download site.
+
+On Linux, check your system's GLIBC version on this site: [repology.org](https://repology.org/project/glibc/versions), or check your GLIBC version with `ldd`:
 
 ```shell
 ldd --version | head -n1
@@ -293,13 +310,13 @@ Required Ruby version: >= 3.1.
 
 **In priority**, refer to the official Ruby documentation:
 
-- [Download Ruby](https://www.ruby-lang.org/en/downloads/)
-- [Installation Guide](https://www.ruby-lang.org/en/documentation/installation/)
+- [Official Ruby Download](https://www.ruby-lang.org/en/downloads/)
+- [Official Ruby Installation Guide](https://www.ruby-lang.org/en/documentation/installation/)
 
 For convenience, you may refer to the following sections for a proposed method for specific operating systems.
 
 Latest version of `ascli` requires a Ruby version [at least under maintenance support](https://www.ruby-lang.org/en/downloads/branches/).
-If only an older Ruby version is available due to system constraints, then use an older version of `ascli` that supports it.
+If only an older Ruby version must be used due to system constraints, then use an older version of `ascli` that supports it.
 
 #### Windows: Installer
 
@@ -321,46 +338,46 @@ Download the Ruby installer executable from <https://rubyinstaller.org/downloads
 rubyinstaller-devkit-3.2.2-1-x64.exe /silent /currentuser /noicons /dir=C:\aspera-cli
 ```
 
-#### macOS: `brew`
+#### Windows: Chocolatey
+
+If you use [Chocolatey](https://chocolatey.org/), then install Ruby with:
+
+```powershell
+choco install ruby
+```
 
-**macOS** comes with Ruby 2.6.
-It is an old unsupported version and [Apple has deprecated it](https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes).
-It will be removed from macOS in the future.
-Do not use it.
+#### macOS: `brew`
 
-The recommended way is to use [Homebrew](https://brew.sh/).
+If you use [Homebrew](https://brew.sh/), then install Ruby with:
 
 ```shell
 brew install ruby
 ```
 
+> [!NOTE]
+> This is the recommended method.
+
+> [!WARNING]
+> **macOS** comes with Ruby 2.6.
+> It is an old unsupported version and [Apple has deprecated it](https://developer.apple.com/documentation/macos-release-notes/macos-catalina-10_15-release-notes).
+> It will be removed from macOS in the future.
+> Do not use it.
+> Use the required version of Ruby.
+
 This installs a recent Ruby suitable for `ascli`.
 
-To add PATH to Ruby on Apple Silicon, add this in your shell configuration file (e.g. `~/.bash_profile` or `~/.zshrc`):
-
-```shell
-use_ruby(){
-    local version=$1
-    case $version in list) for r in $(brew list -1 | grep '^ruby'); do
-      echo "$(brew info --json=v1 $r | jq -r '.[0].installed[0].version') : use_ruby $r"
-    done|gsort -k1,1V;return;;; esac
-    local prefix=$(brew --prefix ruby${version:+@}$version)
-    if ! test -d "$prefix";then
-        echo "No such ruby version: $version"
-        brew list|grep ruby
-        return 1
-    fi
-    PATH="$prefix/bin:$(echo "$PATH" | tr ':' '\n' | grep -v '/ruby' | paste -sd ':' -)"
-    PATH="$(gem env gemdir)/bin:$PATH"
-    export LDFLAGS="-L$prefix/lib"
-    export CPPFLAGS="-I$prefix/include"
-    export PKG_CONFIG_PATH="$prefix/lib/pkgconfig"
-    echo "Using: $prefix"
-    ruby -v
-}
-use_ruby
+To add PATH to Ruby on Apple Silicon, add the following lines to your shell configuration file (i.e. `~/.zshrc` if you are using `zsh`, or `~/.bash_profile` for `bash`):
+
+```shell
+export PATH="$(brew --prefix ruby)/bin:$PATH"
+export PATH="$(gem env gemdir)/bin:$PATH"
 ```
 
+> [!NOTE]
+> Two separate lines are needed because the second one depends on the first one.
+> This is what is displayed at the end of the installation of the ruby tap,
+> same as message from: `brew info ruby`
+
 #### Linux: Package
 
 If your Linux distribution provides a standard Ruby package, you can use it provided that the version supported.
@@ -385,10 +402,11 @@ If your Linux distribution provides a standard Ruby package, you can use it prov
   dnf install -y make automake gcc gcc-c++ kernel-devel
   ```
 
-- Enable the Ruby version you want:
+- Enable the Ruby version you selected:
 
   ```shell
-  dnf module -y enable ruby:3.1
+  dnf module -y enable ruby:3.2
+
   dnf install -y ruby-devel
   ```
 
@@ -411,7 +429,7 @@ apt install -y ruby ruby-dev rubygems ruby-json
 One can remove all installed gems, for example to start fresh:
 
 ```shell
-gem uninstall -axI $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u)
+ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u|xargs gem uninstall -axI
 ```
 
 #### Unix-like: RVM: Single user installation (not root)
@@ -569,27 +587,33 @@ Those are not installed as part of dependencies because they involve compilation
 See [Gemfile](Gemfile):
 
 | name | version | comment |
-| ---- | ------- | ------- |
+|----------------------|---------|-----------------------------------------------------|
 | grpc | ~> 1.71 | (no jruby) for Aspera Transfer Daemon |
-| mimemagic | ~> 0.4 | for preview |
+| marcel | ~> 1.1 | for preview |
 | rmagick | ~> 6.1 | (no jruby) for terminal view |
 | symmetric-encryption | ~> 4.6 | for encrypted hash file secrets |
 | bigdecimal | ~> 3.1 | if RUBY_VERSION >= '3.4' for symmetric-encryption ? |
 | sqlite3 | ~> 2.7 | (no jruby) for async DB |
 | jdbc-sqlite3 | ~> 3.46 | (jruby) for async DB |
 | sequel | ~> 5.96 | (jruby) for async DB |
+| ed25519 | ~> 1.4 | (no jruby) for ed25519 and OpenSSH file format |
+| bcrypt_pbkdf | ~> 1.1 | (no jruby) for ed25519 and OpenSSH file format |
+| syslog | ~> 0.3 | (no jruby) for logger=syslog |
 
 Install like this:
 
 ```shell
 gem install grpc -v '~> 1.71'
-gem install mimemagic -v '~> 0.4'
+gem install marcel -v '~> 1.1'
 gem install rmagick -v '~> 6.1'
 gem install symmetric-encryption -v '~> 4.6'
 gem install bigdecimal -v '~> 3.1'
 gem install sqlite3 -v '~> 2.7'
 gem install jdbc-sqlite3 -v '~> 3.46'
 gem install sequel -v '~> 5.96'
+gem install ed25519 -v '~> 1.4'
+gem install bcrypt_pbkdf -v '~> 1.1'
+gem install syslog -v '~> 0.3'
 ```
 
 ### Ruby Gem: `aspera-cli`
@@ -597,7 +621,7 @@ gem install sequel -v '~> 5.96'
 Once you have Ruby and rights to install gems, install the `aspera-cli` gem and its dependencies:
 
 ```shell
-gem install aspera-cli
+gem install aspera-cli --pre
 ```
 
 To upgrade to the latest version:
@@ -634,20 +658,35 @@ The user installs the gem with `HighSecurity` or `MediumSecurity`: this will suc
 gem install -P MediumSecurity aspera-cli
 ```
 
+#### Beta release of gem
+
+Beta version of gem can be found here: <https://ibm.biz/aspera-cli-beta>
+
+On Linux/macOS, install in a terminal:
+
+```shell
+curl -sLo aspera-cli-beta.gem https://ibm.biz/aspera-cli-beta
+gem install aspera-cli-beta.gem
+```
+
+On Windows, download the link, that saves the file: `aspera-cli-beta.gem`, then install with `gem install aspera-cli-beta.gem`.
+
 ### FASP Protocol: `ascp`
 
-Most file transfers will be executed using the **FASP** protocol, using `ascp`.
-Only two additional files are required to perform an Aspera Transfer, which are part of Aspera Transfer Daemon:
+File transfers are primarily performed using the **FASP** protocol via the `ascp` utility.
 
-- `ascp`
-- `aspera-license` (in same folder, or `../etc`)
+To execute an Aspera transfer, only two additional files are required, both included with the Aspera Transfer Daemon:
+
+- `ascp` - the transfer executable
 
-This can be installed either be installing an Aspera transfer software or using an `ascli` command.
+- `aspera-license` - the license file (located in the same directory as `ascp` or in `../etc`)
+
+These components can be installed either by installing the Aspera transfer software or by running the `ascli` command.
 
 #### Installation of `ascp` through `transferd`
 
 The easiest option to install `ascp` is through the use of the IBM Aspera Transfer Daemon (`transferd`).
-Install using `ascli` for the current platform with:
+Install it using `ascli` (for the current platform) with:
 
 ```shell
 ascli config transferd install
@@ -671,8 +710,8 @@ The installation of the transfer binaries follows those steps:
   - By default, the archive is extracted to `$HOME/.aspera/sdk`.
   - The destination folder can be changed by setting the `sdk_folder` option.
 
-| Option          | Default | Description |
-|-----------------|---------|-------------|
+| Option          | Default | Description                                            |
+|-----------------|---------|--------------------------------------------------------|
 | `sdk_url`       | `DEF`   | URL to download the Aspera Transfer Daemon archive.<br/>`DEF` means: select from available archives. |
 | `locations_url` | `https://ibm.biz/sdk_location` | URL to get download URLs of Aspera Transfer Daemon from IBM official repository. |
 | `sdk_folder`    | `$HOME/.aspera/sdk` | Folder where the SDK archive is extracted. |
@@ -713,6 +752,7 @@ If the embedded method is not used, the following packages are also suitable:
 
 - IBM Aspera Connect Client (Free)
 - IBM Aspera Desktop Client (Free)
+- IBM Aspera for Desktop (Free)
 - IBM Aspera High Speed Transfer Server (Licensed)
 - IBM Aspera High Speed Transfer Endpoint (Licensed)
 
@@ -733,14 +773,15 @@ Refer to section: [Transfer Agents](#transfer-clients-agents)
 
 #### Gem files and dependencies
 
-The sample script: [windows/build_package.sh](windows/build_package.sh) can be used to download all necessary gems and dependencies in a `tar.gz`.
-
-```shell
-./build_package.sh aspera-cli 4.18.0
-```
+Necessary gems can be packed in a `tar.gz` like this:
 
-```text
-Archive: aspera-cli-4.18.0-gems.tgz
+```bash
+mkdir temp_folder
+gem install aspera-cli:4.25.0.pre --no-document --install-dir temp_folder
+find temp_folder
+mv temp_folder/cache aspera-cli-4.25.0.pre-gems
+rm -fr temp_folder
+tar zcvf aspera-cli-4.25.0.pre-gems aspera-cli-4.25.0.pre-gems.tgz
 ```
 
 #### Unix-like
@@ -820,7 +861,7 @@ ascli config ascp install --sdk-url=file:///sdk.zip
 ```
 
 > [!NOTE]
-> An example of installation script is provided: [windows/install.bat](windows/install.bat)
+> A beta version of a packaged installed is available.
 
 ### Container
 
@@ -863,7 +904,7 @@ That is simple, but there are limitations:
 
 #### Container: Details
 
-The container image is built from this [Dockerfile](container/Dockerfile.tmpl.erb).
+The container image is built from this [Dockerfile](build/container/Dockerfile.tmpl.erb).
 The entry point is `ascli` and the default command is `help`.
 
 The container can be executed for individual commands like this: (add `ascli` commands and options at the end of the command line, e.g. `-v` to display the version)
@@ -885,7 +926,7 @@ ascli -v
 ```
 
 ```text
-4.24.1
+4.25.0.pre
 ```
 
 In order to keep persistency of configuration on the host, you should specify your user's configuration folder as a volume for the container.
@@ -1275,7 +1316,7 @@ It's up to the program to split arguments:
 - [Windows: How Command Line Parameters Are Parsed](https://daviddeley.com/autohotkey/parameters/parameters.htm#RUBY)
 - [Understand Quoting and Escaping of Windows Command Line Arguments](https://web.archive.org/web/20190316094059/http://www.windowsinspired.com/understanding-the-command-line-string-and-arguments-received-by-a-windows-program/)
 
- is a Ruby program, so Ruby parses the command line (receibed with `GetCommandLineW`) into arguments and provides them to the Ruby code (`$0` and `ARGV`).
+ is a Ruby program, so Ruby parses the command line (received with `GetCommandLineW`) into arguments and provides them to the Ruby code (`$0` and `ARGV`).
 Ruby vaguely follows the Microsoft C/C++ parameter parsing rules.
 (See `w32_cmdvector` in Ruby source [`win32.c`](https://github.com/ruby/ruby/blob/master/win32/win32.c#L1766)) : <!--cspell:disable-line-->
 
@@ -1312,12 +1353,12 @@ Basically it handles I/O redirection (`<>|`), shell variables (`%`), multiple co
 Eventually, all those special characters are removed from the command line unless escaped with `^` or `"`.
 `"` are kept and given to the program.
 
-#### Shell parsing for Windows: Powershell
+#### Shell parsing for Windows: PowerShell
 
-For Powershell, it actually depends on the version of it (7.3+).
+For PowerShell, it actually depends on the version of it (5.1, 7.3+).
 
-A difficulty is that Powershell parses the command line for its own use and manages special characters, but then it passes the command line to the program (Ruby) as a single string, possibly without the special characters.
-Since we usually do not use powershell features, it is advised to use the "stop-parsing" token `--%`.
+A difficulty is that PowerShell parses the command line for its own use and manages special characters, but then it passes the command line to the program (Ruby) as a single string, possibly without the special characters.
+If not using PowerShell features (e.g. variable), one can use the "stop-parsing" token `--%`.
 
 Details can be found here:
 
@@ -1325,22 +1366,87 @@ Details can be found here:
 
 - [quoting rules](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_quoting_rules)
 
-The following examples give the same result on Windows using Powershell:
+##### PowserShell 5
+
+- Check your powershell version:
+
+```powershell
+$psversiontable.psversion.Major
+```
+
+```text
+5
+```
+
+The following examples give the same result on Windows using PowerShell 5:
+
+```text
+╭───────┬───────╮
+│ field │ value │
+╞═══════╪═══════╡
+│ x     │ true  │
+│ k     │ v     │
+╰───────┴───────╯
+```
+
+- Use PowerShell argument `--%` to place PowerShell in "stop-parsing" mode.
 
 ```powershell
-PS C:\> echo $psversiontable.psversion
+ascli config echo  --% @json:'{"k":"v","x":true}'
+```
+
+- Triple double quotes are replaced with a single double quote in normal mode:
 
-Major  Minor  Build  Revision
------  -----  -----  --------
-5      1      19041  4046
+```powershell
+ascli config echo @json:'{"""k""":"""v""","""x""":true}'
+```
 
-PS C:\> ascli config echo  --% @json:'{"k":"v","x":"y"}'
+- To insert PowerShell variables in the JSON string, one can do:
 
-PS C:\> ascli config echo @json:'{"""k""":"""v""","""x""":"""y"""}'
+```powershell
+$var="v"
+ascli conf echo  $('@json:{"""k""":"""' + $var + '""","""x""":true}')
 ```
 
-> [!NOTE]
-> The special Powershell argument `--%` places Powershell in "stop-parsing" mode.
+##### PowserShell 7
+
+- Check your powershell version:
+
+```powershell
+$psversiontable.psversion.Major
+```
+
+```text
+7
+```
+
+The following examples give the same result on Windows using PowerShell 7:
+
+- Use PowerShell argument `--%` to place PowerShell in "stop-parsing" mode.
+
+```powershell
+ascli config echo  --% @json:{"k":"v","x":true}
+```
+
+- Single quote protects double quote in normal mode:
+
+```powershell
+ascli config echo @json:'{"k":"v","x":true}'
+```
+
+- To insert PowerShell variables in the JSON string, one can do:
+
+```powershell
+$var="v"
+ascli conf echo  $('@json:{"k":"' + $var + '","x":true}')
+```
+
+- Use PowerShell structure and then convert to JSON string:
+
+```powershell
+$var="v"
+ascli conf echo "@json:$(@{ k = $var; x = $true } | ConvertTo-Json -Compress)"
+```
 
 #### Extended Values (JSON, Ruby, ...)
 
@@ -1366,7 +1472,7 @@ ascli config echo 1 2 3
 ERROR: Argument: unprocessed values: ["2", "3"]
 ```
 
-`config echo` displays the value of the **first** argument using Ruby syntax: it surrounds a string with `"` and add `\` before special characters.
+`config echo` displays the value of the **first** argument using the current output `format`.
 
 > [!NOTE]
 > It gets its value after shell command line parsing and `ascli` extended value parsing.
@@ -1379,7 +1485,7 @@ Depending on the case, a different `format` option is used to display the actual
 For example, in the simple string `Hello World`, the space character is special for the shell, so it must be escaped so that a single value is represented.
 
 Double quotes are processed by the shell to create a single string argument.
-For **POSIX shells**, single quotes can also be used in this case, or protect the special character ` ` (space) with a backslash. <!-- markdownlint-disable-line -->
+For **POSIX shells**, single quotes can also be used in this case, or protect the special character ` ` (space) with a backslash.
 
 ```shell
 ascli config echo "Hello World" --format=text
@@ -1398,7 +1504,7 @@ Even if the variable contains spaces it results only in one argument for `ascli`
 
 > [!NOTE]
 > We use a simple shell variable in this example.
-> Note that it does not need to be exported as an environment variable.
+> It does not need to be exported as an environment variable.
 
 ```shell
 MYVAR="Hello World"
@@ -1564,7 +1670,7 @@ The value of **Options** and **Positional Arguments** is evaluated with the [Ext
 - **Commands**, typically at the beginning
 - **Command Parameters**, mandatory arguments, e.g. creation data or entity identifier
 
-When options are removed from the command line, the remaining arguments are typically **Positional Arguments** with a pre-defined order.
+When options are removed from the command line, the remaining arguments are typically **Positional Arguments** with a significant, pre-defined order.
 
 **Commands** are typically entity types (e.g. `users`) or verbs (e.g. `create`) to act on those entities.
 Its value is a `String` that must belong to a fixed list of values in a given context.
@@ -1581,14 +1687,13 @@ ascli config ascp info
 - `info` is the third level command: action to be performed
 
 Typically, **Commands** are located at the **beginning** of the command line.
-Order is significant.
 The provided command must match one of the supported commands in the given context.
 If wrong, or no command is provided when expected, an error message is displayed and the list of supported commands is displayed.
 
 Standard **Commands** are: `create`, `show`, `list`, `modify`, `delete`.
 Some entities also support additional commands.
 When those additional commands are related to an entity also reachable in another context, then those commands are located below command `do`.
-For example sub-commands appear after entity selection (identifier), e.g. `ascli aoc admin node do 1234 browse /`: `browse` is a sub-command of `node`.
+For example sub-commands appear after entity selection (identifier), e.g. `ascli aoc admin node do <node_id> browse /`: `browse` is a sub-command of `node`.
 
 **Command Parameters** are typically mandatory values for a command, such as entity creation data or entity identifier.
 
@@ -1603,6 +1708,29 @@ If a **Command Parameter** begins with `-`, then either use the `@val:` syntax (
 
 A few **Command Parameters** are optional, they are always located at the end of the command line.
 
+A special Extended Value `@:` has the following meaning:
+
+- Take all remaining positional arguments
+- Expect each of them to have the format: `<path>=<value>`
+- `<path>` designates a path in a complex structure such as Hash or Array.
+  `.` is the path separator.
+  Each segment separated by a dot represents a key in a nested structure.
+  Integer index denote Array, and other denote Hash index.
+- `ascli` tries to convert `<value>` to the simplest type (bool, int, float, string).
+  If a specific type is required, it can be specified using the `@json:` or `@ruby:` syntax.
+  For example, `--a.b.c=1` is equivalent to `--a=@json'{"b":{"c":1}}'`.
+  This allows specifying nested keys directly on the command line using a concise **dot-separated** syntax.
+
+Example:
+
+```bash
+ascli conf echo @: a.b=1 a.c=2 a.d.0=hello a.d.1=world --format=json
+```
+
+```json
+{"a":{"b":1,"c":2,"d":["hello","world"]}}
+```
+
 #### Options
 
 Command-line options, such as `--log-level=debug`, follow these conventions:
@@ -1634,13 +1762,17 @@ Exceptions and Special Cases:
 - **Option Terminator**:
   The special option `--` ends option parsing.
   All subsequent arguments, including those starting with `-`, are treated as positional arguments.
-- **Dot Notation for Hashes**:
+- **Dot Notation for Hash and Array**:
   If an option name contains a dot (`.`), it is interpreted as a `Hash`.
   Each segment separated by a dot represents a key in a nested structure.
   `ascli` tries to convert the value to the simplest type (bool, int, float, string).
   If a specific type is required, it can be specified using the `@json:` or `@ruby:` syntax.
   For example, `--a.b.c=1` is equivalent to `--a=@json'{"b":{"c":1}}'`.
   This allows specifying nested keys directly on the command line using a concise **dot-separated** syntax.
+- **Cummulative Hashes**:
+  When an option of type `Hash` is set, the value is deep-merged to an existing or default value.
+  Setting to `@none:` is equivalent to setting to `@json:{}`, i.e. an empty `Hash`.
+  This can be used to start from an empty value, and not used existing default value.
 
 Example:
 
@@ -1672,6 +1804,7 @@ The value for **any** options can come from the following locations (in this ord
 Environment variable starting with prefix: ASCLI_ are taken as option values, e.g. `ASCLI_OPTION_NAME` is for `--option-name`.
 
 Option `show_config` dry runs the configuration, and then returns currently set values for options.
+
 `ascli --show-config` outputs global options only, and `ascli [plugin] --show-config` outputs global and plugin default options.
 In addition, option `--show-config` can be added at the end of any full command line, this displays the options that would be used for the command.
 
@@ -1704,8 +1837,8 @@ To redirect results to a file, use option `output`.
 
 Depending on action, the output will contain:
 
-| Result Type     | Description |
-|-----------------|-------------------|
+| Result Type     | Description                                                                       |
+|-----------------|-----------------------------------------------------------------------------------|
 | `single_object` | Displayed as a 2 dimensional table: one line per field, first column is field name, and second is field value. Nested hashes are collapsed. |
 | `object_list`   | Displayed as a 2 dimensional table: one line per item, one column per field. |
 | `value_list`    | A table with one column. |
@@ -1713,47 +1846,75 @@ Depending on action, the output will contain:
 | `status`        | A message. |
 | `other_struct`  | A complex structure that cannot be displayed as an array. |
 
+#### Enhanced display of special values
+
+Special values are highlighted as follows in `format=table`:
+
+| Value          | Display          |
+|----------------|------------------|
+| `nil`          | `<null>`         |
+| empty `String` | `<empty string>` |
+| empty `Array`  | `<empty list>`   |
+| empty `Hash`   | `<empty dict>`   |
+
+Example:
+
+```shell
+ascli config echo @json:'{"ni":null,"es":"","ea":[],"eh":{}}'
+```
+
+```text
+╭───────┬────────────────╮
+│ field │ value          │
+╞═══════╪════════════════╡
+│ ni    │ <null>         │
+│ es    │ <empty string> │
+│ ea    │ <empty list>   │
+│ eh    │ <empty dict>   │
+╰───────┴────────────────╯
+```
+
 #### Option: `format`
 
 The style of output can be set using the `format` option:
 
-| `format` | Output formatting    |
-|----------|----------------------|
-| `table`  | Text table (default) |
-| `text`   | Value as `String`    |
-| `ruby`   | Ruby code            |
-| `json`   | JSON code            |
-| `jsonpp` | JSON pretty printed  |
-| `yaml`   | YAML                 |
-| `csv`    | Comma Separated Values |
-| `image`  | Image URL or data    |
-| `nagios` | Suitable for Nagios  |
+| `format` | Output formatting       |
+|----------|-------------------------|
+| `table`  | Text table (default)    |
+| `text`   | Value as `String`       |
+| `ruby`   | Ruby code               |
+| `json`   | JSON code               |
+| `jsonpp` | JSON pretty printed     |
+| `yaml`   | YAML                    |
+| `csv`    | Comma Separated Values  |
+| `image`  | Image URL or data       |
+| `nagios` | Suitable for Nagios     |
 
 By default, result of type `single_object` and `object_list` are displayed using format `table`.
 
 #### Option: `table_style`
 
-The table style can be customized with option: `table_style` which expects a `Hash`.
+The way `format`: `table` and `csv` are generated can be customized with option: `table_style` which expects a `Hash`.
 
 For `format=table`, options are the ones described in gem [`terminal-table`](https://github.com/tj/terminal-table).
 
-For `format=csv`, options are described in gem [`csv`](https://ruby.github.io/csv/CSV.html#class-CSV-label-Options+for+Generating).
-
 For example, to display a table with thick Unicode borders:
 
 ```shell
 ascli config preset over --table-style=@ruby:'{border: :unicode_thick_edge}'
 ```
 
+> [!NOTE]
+> Other border styles exist, not limited to: `:unicode`, `:unicode_round`.
+
+For `format=csv`, options are described in gem [`csv`](https://ruby.github.io/csv/CSV.html#class-CSV-label-Options+for+Generating).
+
 For example, to display a CSV with headers and quotes:
 
 ```shell
 ascli config echo @json:'[{"name":"foo","id":1},{"name":"bar","id":8}]' --format=csv --table=@json:'{"headers":true,"force_quotes":true}'
 ```
 
-> [!NOTE]
-> Other border styles exist, not limited to: `:unicode`, `:unicode_round`.
-
 #### Option: `flat_hash`: Single level `Hash`
 
 This option controls how object fields are displayed for complex objects.
@@ -1801,57 +1962,29 @@ ascli config echo @json:'{"A":"a","B":[{"name":"B1","value":"b1"},{"name":"B2","
 ╰───────┴────────────────────────────────────────────────────────────────────────╯
 ```
 
-#### Enhanced display of special values
-
-Special values are highlighted as follows::
-
-| Value          | Display          |
-|----------------|------------------|
-| `nil`          | `<null>`         |
-| empty `String` | `<empty string>` |
-| empty `Array`  | `<empty list>`   |
-| empty `Hash`   | `<empty dict>`   |
-
-Example:
-
-```shell
-ascli config echo @json:'{"ni":null,"es":"","ea":[],"eh":{}}'
-```
-
-```text
-╭───────┬────────────────╮
-│ field │ value          │
-╞═══════╪════════════════╡
-│ ni    │ <null>         │
-│ es    │ <empty string> │
-│ ea    │ <empty list>   │
-│ eh    │ <empty dict>   │
-╰───────┴────────────────╯
-```
-
 #### Option: `multi_single`
 
 This option controls how result fields are displayed as columns or lines, when option `format` is set to `table`.
 Default is `no`.
 There are two types of results that are affected by this option:
 
-| Result          | Description |
-|-----------------|-------------|
-| `single_object` | A single item with multiple fields. |
+| Result          | Description                                 |
+|-----------------|---------------------------------------------|
+| `single_object` | A single item with multiple fields.         |
 | `object_list`   | A list of items, each with multiple fields. |
 
 An item (object) is displayed in one of those 2 ways:
 
-| Display    | rows   | columns |
-|------------|--------|---------|
+| Display    | rows   | columns             |
+|------------|--------|---------------------|
 | Simple     | Fields | `field` and `value` |
-| Transposed | Items  | Fields  |
+| Transposed | Items  | Fields              |
 
 The display of result is as follows:
 
-| Result          | `no`       | `yes`      | `single` |
-|-----------------|------------|------------|----------|
-| `single_object` | Simple     | Simple     | Simple   |
+| Result          | `no`       | `yes`       | `single`                            |
+|-----------------|------------|-------------|-------------------------------------|
+| `single_object` | Simple     | Simple      | Simple                              |
 | `object_list`   | Transposed | Simple<br/>(Multiple objects) | Simple if 1 object,<br/>transposed if 2+ objects |
 
 This parameter can be set as a global default with:
@@ -2004,17 +2137,17 @@ In above example, the same result is obtained with option:
 
 Option `select` applies the filter after a possible "flattening" with option: `flat_hash`.
 
-#### Percent selector
+### Percent selector
 
 The percent selector allows identification of an entity by another unique identifier other than the native identifier.
 
 Syntax: `%<field>:<value>`
 
 When a command is executed on a single entity, the entity is identified by a unique identifier that follows the command.
-For example, in the following command, `1234` is the user's identifier:
+For example, in the following command, `_my_user_id_` is the user's identifier:
 
 ```shell
-ascli aoc admin user show 1234
+ascli aoc admin user show _my_user_id_
 ```
 
 Some commands provide the following capability:
@@ -2043,38 +2176,42 @@ Decoders act like a function with its parameter on right-hand side and are recog
 
 The following decoders are supported:
 
-| Decoder  | Parameter| Returns  | Description |
-|----------|----------|----------|-------------|
-| `base64` | `String` | `String` | Decode a base64 encoded string |
-| `csvt`   | `String` | `Array`  | Decode a titled CSV value |
-| `env`    | `String` | `String` | Read from a named env var name, e.g. `--password=@env:MYPASSVAR` |
-| `file`   | `String` | `String` | Read value from specified file (prefix `~/` is replaced with the users home folder), e.g. `--key=@file:~/.ssh/mykey` |
-| `json`   | `String` | Any      | Decode JSON values (convenient to provide complex structures) |
-| `lines`  | `String` | `Array`  | Split a string in multiple lines and return an array |
-| `list`   | `String` | `Array`  | Split a string in multiple items taking first character as separator and return an array |
-| `none`   | None     | Nil      | A null value |
-| `path`   | `String` | `String` | Performs path expansion on specified path (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml` |
+| Decoder  | Parameter| Returns  | Description                                                                              |
+|----------|----------|----------|------------------------------------------------------------------------------------------|
+| `base64` | `String` | `String` | Decode a base64 encoded string. |
+| `csvt`   | `String` | `Array`  | Decode a titled CSV value. |
+| `env`    | `String` | `String` | Read from a named env var name. e.g. `--password=@env:MYPASSVAR` |
+| `file`   | `String` | `String` | Read value from specified file (prefix `~/` is replaced with the users home folder). e.g. `--key=@file:~/.ssh/mykey` |
+| `json`   | `String` | Any      | Decode JSON values. Convenient to provide complex structures. |
+| `lines`  | `String` | `Array`  | Split a string in multiple lines and return an `Array`. |
+| `list`   | `String` | `Array`  | Split a string in multiple items taking first character as separator and return an `Array`. |
+| `none`   | None     | Nil      | A `null` value. |
+| `path`   | `String` | `String` | Performs path expansion on specified path (prefix `~/` is replaced with the user's home folder). e.g. `--config-file=@path:~/sample_config.yml` |
 | `preset` | `String` | `Hash`   | Get whole option preset value by name. Sub-values can also be used, using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]` |
-| `extend` | `String` | `String` | Evaluates embedded extended value syntax in string |
+| `extend` | `String` | `String` | Evaluates embedded extended value syntax in string. |
 | `re`     | `String` | `Regexp` | Ruby Regular Expression (short for `@ruby:/.../`) |
-| `ruby`   | `String` | Any      | Execute specified Ruby code |
-| `secret` | None     | `String` | Ask password interactively (hides input) |
-| `stdin`  | None     | `String` | Read from stdin in text mode (no value on right) |
-| `stdbin` | None     | `String` | Read from stdin in binary mode (no value on right) |
-| `uri`    | `String` | `String` | Read value from specified URL, e.g. `--fpac=@uri:http://serv/f.pac` |
+| `ruby`   | `String` | Any      | Execute specified Ruby code. |
+| `secret` | None     | `String` | Ask password interactively (hides input). |
+| `stdin`  | None     | `String` | Read from stdin in text mode (no value on right). |
+| `stdbin` | None     | `String` | Read from stdin in binary mode (no value on right). |
+| `uri`    | `String` | `String` | Read value from specified URL. e.g. `--fpac=@uri:http://serv/f.pac` |
 | `val`    | `String` | `String` | Prevent decoders on the right to be decoded. e.g. `--key=@val:@file:foo` sets the option `key` to value `@file:foo`. |
-| `yaml`   | `String` | Any      | Decode YAML |
-| `zlib`   | `String` | `String` | Decompress data using zlib |
+| `yaml`   | `String` | Any      | Decode YAML. |
+| `zlib`   | `String` | `String` | Decompress data using zlib. |
+| `p`      | None     | Any      | Parses remaining arguments as `Hash` or `Array`. |
 
 > [!NOTE]
 > A few commands support a value of type `Proc` (lambda expression).
-> For example, the **Extended Value** `@ruby:'->(i){i["attr"]}'` is a lambda expression that returns the value for key `attr` of the `Hash` `i`.
+> For example, the **Extended Value** `@ruby:'->(i){i["attr"]}'` is a lambda expression that returns the value for key `attr` of the `Hash` parameter named `i`.
 
 To display the result of an extended value, use the `config echo` command.
 
 The `extend` decoder is useful to evaluate embedded extended value syntax in a string.
 It expects a `@` to close the embedded extended value syntax.
 
+Option `parser` allows definition of a default parser when the positinal parameter or option expects a `Hash` or `Array`.
+For example, with `--parser=json`, the parameter `{}` will be parsed as an empty JSON Hash, even without prefix `@json:`.
+
 Example: Create a `Hash` value with the convenient `@json:` decoder:
 
 ```shell
@@ -2151,15 +2288,17 @@ EOF
 {"key1":"value1","key2":["item1","item2"],"key3":{"key4":"value4","key5":"value5"}}
 ```
 
-### Configuration and Persistency Folder
+### Main, configuration and Persistency Folder
 
-`ascli` configuration and persistency files (token cache, file lists, persistency files) are stored by default in `[User's home folder]/.aspera/ascli`.
+`ascli` looks for configuration and persistency files (token cache, file lists, persistency files) in the folder specified using option `home`.
+The default value is `[User's home folder]/.aspera/ascli`.
 
 > [!NOTE]
-> `[User's home folder]` is found using Ruby's `Dir.home` (`rb_w32_home_dir`).
-> It uses the `HOME` env var primarily, and on MS Windows it also looks at `%HOMEDRIVE%%HOMEPATH%` and `%USERPROFILE%`.
-> `ascli` sets the env var `%HOME%` to the value of `%USERPROFILE%` if set and exists.
-> So, on Windows `%USERPROFILE%` is used as it is more reliable than `%HOMEDRIVE%%HOMEPATH%`.
+> The `[User's home folder]` is determined using Ruby’s `Dir.home` method.
+> Primary source: The HOME environment variable.
+> On Windows: Ruby also checks `%HOMEDRIVE%%HOMEPATH%` and `%USERPROFILE%` (via `rb_w32_home_dir`).
+> Additionally, `ascli` sets the `%HOME%` environment variable to the value of `%USERPROFILE%` if it exists and is valid.
+> Therefore, on Windows, `%USERPROFILE%` is preferred because it is generally more reliable than `%HOMEDRIVE%%HOMEPATH%`.
 
 The configuration folder can be displayed using :
 
@@ -2172,9 +2311,11 @@ ascli config folder
 ```
 
 > [!NOTE]
-> This is equivalent to: `ascli --show-config --fields=home`
+> This is equivalent to display the value of the `home` option.
 
-It can be overridden using option `home`.
+```shell
+ascli --show-config --fields=home
+```
 
 Example (Windows):
 
@@ -2186,11 +2327,28 @@ ascli config folder
 C:\Users\Kenji\.aspera\ascli
 ```
 
-When OAuth is used (AoC, Faspex5) `ascli` keeps a cache of generated bearer tokens in folder `persist_store` in configuration folder by default.
+When OAuth is used (AoC, Faspex5) `ascli` keeps a cache of generated bearer tokens in folder `persist_store` located in the configuration folder by default.
 Option `cache_tokens` (**yes**/no) allows controlling if OAuth tokens are cached on file system, or generated for each request.
 The command `config tokens flush` clears that cache.
 Tokens are kept on disk for a maximum of 30 minutes (`TOKEN_CACHE_EXPIRY_SEC`) and garbage collected after that.
-When a token has expired, then a new token is generated, either using a refresh_token if it is available, or by the default method.
+When a token has expired, then a new token is generated, either using a `refresh_token` if it is available, or by the default method.
+
+### Configuration file
+
+On the first execution of `ascli`, an empty configuration file is created in the configuration folder (`ascli config folder`).
+There is no mandatory information required in this file.
+The use of it is optional as any option can be provided on the command line.
+
+Although the file is a standard `YAML` file, `ascli` provides commands to read and modify it using the `config` command.
+
+All options for `ascli` can be set on command line, or by env vars, or using [Option Preset](#option-preset) in the configuration file.
+
+A configuration file provides a way to define default values, especially for authentication options, thus avoiding to always having to specify those options on the command line.
+
+The default configuration file is: `$HOME/.aspera/ascli/config.yaml` (this can be overridden with option `--config-file=path` or its env var).
+
+The configuration file is a catalog of named lists of options, called: [Option Preset](#option-preset).
+Then, instead of specifying some common options on the command line (e.g. address, credentials), it is possible to invoke the ones of an [Option Preset](#option-preset) (e.g. `mypreset`) using the option `preset`: `--preset=mypreset` or its shortcut: `-Pmypreset`.
 
 ### Invalid Filename Characters
 
@@ -2210,23 +2368,8 @@ The default value is `_<>:"/\|?*`, corresponding to replacement character `_` an
 Some temporary files may be needed during runtime.
 The temporary folder may be specified with option: `temp_folder`.
 Temporary files are deleted at the end of execution unless option: `clean_temp` is set to `no`.
-
-### Configuration file
-
-On the first execution of `ascli`, an empty configuration file is created in the configuration folder (`ascli config folder`).
-There is no mandatory information required in this file.
-The use of it is optional as any option can be provided on the command line.
-
-Although the file is a standard `YAML` file, `ascli` provides commands to read and modify it using the `config` command.
-
-All options for `ascli` can be set on command line, or by env vars, or using [Option Preset](#option-preset) in the configuration file.
-
-A configuration file provides a way to define default values, especially for authentication options, thus avoiding to always having to specify those options on the command line.
-
-The default configuration file is: `$HOME/.aspera/ascli/config.yaml` (this can be overridden with option `--config-file=path` or its env var).
-
-The configuration file is a catalog of named lists of options, called: [Option Preset](#option-preset).
-Then, instead of specifying some common options on the command line (e.g. address, credentials), it is possible to invoke the ones of an [Option Preset](#option-preset) (e.g. `mypreset`) using the option `preset`: `--preset=mypreset` or its shortcut: `-Pmypreset`.
+By default (`@sys`), the temporary folder is the system's temporary folder for the current user (Ruby `Etc.systmpdir`).
+A special value of `@env` will set the folder to Ruby `Dir.tmpdir` which uses regular env var to set the temp folder.
 
 #### Option Preset
 
@@ -2325,7 +2468,7 @@ ascli config preset get default _plugin_name_
 "_default_preset_for_plugin_"
 ```
 
-#### Plugin: `config`: Configuration
+### Plugin: `config`: Configuration
 
 Plugin `config` provides general commands for `ascli`:
 
@@ -2371,7 +2514,7 @@ ascli config preset set GLOBAL version_check_days 0
 ascli config preset set default config my_common_defaults
 ```
 
-### Tested commands for `config`
+#### Tested commands for `config`
 
 > [!NOTE]
 > Add `ascli config` in front of the following commands:
@@ -2394,11 +2537,14 @@ ascp show
 ascp spec
 check_update
 coffee
+coffee --log-level=trace2 --log-format=caller
 coffee --ui=text
 coffee --ui=text --image=@json:'{"text":true,"double":false}'
 coffee --ui=text --image=@json:'{"text":true}'
 detect https://faspex5.example.com/path
+detect https://faspex5.example.com/path faspex5
 detect https://node.example.com/path
+detect https://server.example.com/path server
 detect https://shares.example.com/path shares
 detect https://tst.example.com/path faspio
 detect https://tst.example.com/path httpgw
@@ -2415,10 +2561,12 @@ echo @json:'[{"user":{"id":1,"name":"foo"},"project":"bar"}]' --multi-single=yes
 echo @lines:@stdin:
 echo @list:,1,2,3
 echo @secret:
+echo @stdbin:
 echo @uri:/etc/hosts
 echo @uri:file:/etc/hosts
 echo @uri:http://ifconfig.me
 echo @uri:https://ifconfig.me
+echo @uri:https://ifconfig.me/ip --cert-stores=@ruby:[OpenSSL::X509::DEFAULT_CERT_DIR,OpenSSL::X509::DEFAULT_CERT_FILE] --http-options.ssl_options=@list:,CIPHER_SERVER_PREFERENCE,-NETSCAPE_CA_DN_BUG --insecure=yes
 echo @vault:my_preset.password
 echo @zlib:@stdin:
 echo hello
@@ -2437,7 +2585,7 @@ genkey my_key 4096
 image https://eudemo.asperademo.com/wallpaper.jpg
 initdemo
 open
-plugins create my_command
+plugins create my_command .
 plugins list
 preset delete conf_name
 preset initialize conf_name @json:'{"p1":"v1","p2":"v2"}'
@@ -2455,9 +2603,9 @@ remote_certificate chain https://node.example.com/path
 remote_certificate name https://node.example.com/path
 remote_certificate only https://node.example.com/path
 smtp_settings
+sync spec
 tokens flush
 tokens list
-tokens show foobar
 transferd install
 transferd list
 vault create @json:'{"label":"my_label","password":"my_password_here","description":"my secret"}'
@@ -2470,12 +2618,14 @@ wizard https://faspex4.example.com/path faspex --username=test --password=test
 wizard https://faspex5.example.com/path faspex5 --key-path=my_private_key
 wizard https://node.example.com/path node --username=test --password=test
 wizard https://orch.example.com/path orchestrator --username=test --password=test
+wizard https://server.example.com/path server --username=my_username --password=my_password
 wizard https://shares.example.com/path shares --username=test --password=test
-wizard my_org aoc --key-path=my_private_key --username=my_user_email
+wizard https://tst.example.com/path faspio --username=my_username --password=my_password
 wizard my_org aoc --key-path=my_private_key --username=my_user_email --use-generic-client=yes
+wizard my_org aoc mypreset --key-path=my_private_key --username=my_user_email
 ```
 
-#### Format of file
+#### Format of configuration file
 
 The configuration file is a `Hash` in a YAML file.
 Example:
@@ -2585,20 +2735,21 @@ The wizard is a command that asks the user for information and creates an [Optio
 
 It takes three optional arguments:
 
-- The URL of the application, else it will ask for it;
-- The plugin name: it limits detection to a given plugin, else it will try to detect known plugins from the URL
-- The preset name: it will create a new [Option Preset](#option-preset) with this name, else it will use specific information to generate a unique preset name.
+|#| Parameter description                      | If not provided, `ascli`                 |
+|-|--------------------------------------------|--------------------------------------------|
+|1| **URL** or hostname of the application     | ask for it.                                |
+|2| The **plugin name** to limit search to     | tries to detect known plugins from the URL |
+|3| The **preset name** to save in config file | generates a unique preset name             |
 
-Special options are also available to the wizard:
+Options are also available for the wizard:
 
-| Option      | Value    | Description |
-|-------------|----------|-------------|
-| `default`   | [yes]/no | Set as default configuration for specified plugin. |
+| Option      | Value    | Description                                                         |
+|-------------|----------|---------------------------------------------------------------------|
+| `default`   | [yes]/no | Set as default configuration for specified plugin.                  |
 | `override`  | yes/[no] | Override existing default preset name for the plugin, if it exists. |
-| `key-path`  | path     | Path to private key for JWT.    |
-| `test-mode` | yes/[no] | Skip private key check step.    |
+| `key_path`  | path     | Path to private key for JWT.                                        |
 
-Other options can be provided to the wizard, such as `--username`, etc...
+Other plugin-specific options can be provided to the wizard, such as `--username`, etc...
 They will be added to the [Option Preset](#option-preset) created by the wizard.
 
 The simplest invocation is:
@@ -2607,6 +2758,9 @@ The simplest invocation is:
 ascli config wizard
 ```
 
+If the application requires a private key, the user can either provide the path to it with option `key_path`.
+The user is told where to place the associated public pey PEM in the application.
+
 #### Example of configuration for a plugin
 
 For Faspex, Shares, Node (including ATS, Aspera Transfer Service), Console,
@@ -2713,8 +2867,8 @@ brew install hashicorp/tap/vault
 vault server -dev -dev-root-token-id=dev-only-token
 ```
 
-| Parameter | Example  | Description |
-|-----------|----------|-------------|
+| Parameter | Example                 | Description                                                         |
+|-----------|-------------------------|---------------------------------------------------------------------|
 | `type`    | `vault`                 | The type of the vault |
 | `url`     | `http://127.0.0.1:8200` | The URL of the vault  |
 | `token`   | `dev-only-token`        | The token for the vault, by default uses parameter `vault_password` |
@@ -2730,10 +2884,10 @@ vault server -dev -dev-root-token-id=dev-only-token
 
 It is possible to manage secrets in macOS keychain (only read supported currently).
 
-| Parameter | Example  | Description |
-|-----------|----------|-------------|
-| `type`    | `system` | The type of the vault |
-| `name`    | ``ascli``  | The name of the keychain to use |
+| Parameter | Example     | Description                        |
+|-----------|-------------|------------------------------------|
+| `type`    | `system`    | The type of the vault.             |
+| `name`    | ``ascli`` | The name of the keychain to use.   |
 
 ```shell
 --vault=@json:'{"type":"system","name":"ascli"}'
@@ -2747,10 +2901,10 @@ It is possible to store and use secrets encrypted in a file using option `vault`
 {"type":"file","name":"vault.bin"}
 ```
 
-| Parameter | Example      | Description |
-|-----------|--------------|-------------|
-| `type`    | `file`       | The type of the vault |
-| `name`    | `vault.bin`  | File path, absolute, or relative to the configuration folder `ASCLI_HOME` |
+| Parameter | Example      | Description                                                        |
+|-----------|--------------|--------------------------------------------------------------------|
+| `type`    | `file`       | The type of the vault.                                             |
+| `name`    | `vault.bin`  | File path, absolute, or relative to the configuration folder `ASCLI_HOME`. |
 
 #### Vault: Operations
 
@@ -2806,7 +2960,16 @@ It consists in using a pair of associated keys: a private key and a public key.
 The same pair can be used for multiple applications.
 The file containing the private key (key pair) can optionally be protected by a passphrase.
 If the key is protected by a passphrase, then it will be prompted when used.
-(some plugins support option `passphrase`)
+Some plugins support option `passphrase`.
+
+By default, `ascli` does not support `ed25519` type, nor OpenSSH encoded keys.
+See section: [Private key type ed25519](#private-key-type-ed25519-not-supported-by-default).
+It requires PEM encoded keys.
+To support `ed25519` and OpenSSH format (default on modern Linux), install those gems:
+
+```shell
+gem install ed25519 bcrypt_pbkdf
+```
 
 The following sample commands use the shell variable `KEY_PAIR_PATH`.
 Set it to the desired safe location of the private key.
@@ -2827,6 +2990,7 @@ If another format is used, such as `DER`, it can be converted to `PEM`, e.g. usi
 
 The generated key is of type `RSA`, by default: **4096** bit.
 For convenience, the public key is also extracted with extension `.pub`.
+Files are PEM encoded.
 The key is not passphrase protected.
 
 ```shell
@@ -2888,12 +3052,12 @@ This server can server HTTP or HTTPS (with certificate):
 
 The following parameters are supported:
 
-| Parameter         | Type     | Default | Description                                         |
-|-------------------|----------|---------|-----------------------------------------------------|
-| `url`             | `String` | `http://localhost:8080` | Base URL on which requests are listened, a path can be provided.           | <!-- markdownlint-disable-line -->
-| `cert`            | `String` | -       | (HTTPS) Path to certificate file (with ext. `.pfx` or `.p12` for PKCS12) |
-| `key`             | `String` | -       | (HTTPS) Path to private key file (PEM), or passphrase for PKCS12           |
-| `chain`           | `String` | -       | (HTTPS) Path to certificate chain (PEM only)                         |
+| Parameter         | Type     | Default                 | Description                                                      |
+|-------------------|----------|-------------------------|------------------------------------------------------------------|
+| `url`             | `String` | `http://localhost:8080` | Base URL on which requests are listened, a path can be provided. | <!-- markdownlint-disable-line -->
+| `cert`            | `String` | -       | (HTTPS) Path to certificate file (with ext. `.pfx` or `.p12` for `PKCS12`).        |
+| `key`             | `String` | -       | (HTTPS) Path to private key file (PEM), or passphrase for `PKCS12`.                |
+| `chain`           | `String` | -       | (HTTPS) Path to certificate chain (PEM only).                                    |
 
 Parameter `url` (base URL) defines:
 
@@ -2913,12 +3077,12 @@ This is available:
 
 The following options can be specified in the option `image`:
 
-| Option     | Type    | Description |
-|------------|---------|-------------|
-| reserve    | `Integer` | Lines reserved to display a status |
-| text       | `Bool`    | Display text instead of image|
-| double     | `Bool`    | Display double text resolution (half characters) |
-| font_ratio | `Float`   | Font height/width ratio in terminal |
+| Option     | Type      | Description                                       |
+|------------|-----------|---------------------------------------------------|
+| reserve    | `Integer` | Lines reserved to display a status.               |
+| text       | `Bool`    | Display text instead of image.                    |
+| double     | `Bool`    | Display double text resolution (half characters). |
+| font_ratio | `Float`   | Font height/width ratio in terminal.              |
 
 ```shell
 ascli config image https://eudemo.asperademo.com/wallpaper.jpg --ui=text --image=@json:'{"text":true}'
@@ -2948,38 +3112,47 @@ It is also possible to force the graphical mode with option `--ui` :
 ### Logging, Debugging
 
 The gem is equipped with traces, mainly for debugging and learning APIs.
+The following options control logging:
+
+| Option        | Values | Description                                                             |
+|---------------|--------|-------------------------------------------------------------------------|
+| `logger`      | `stdout`<br/>`stderr`<br/>`syslog` | Type of output.<br/>Default: `stderr` |
+| `log_level`   | `trace2`<br/>`trace1`<br/>`debug`<br/>`info`<br/>`warn`<br/>`error` | Minimum level displayed.<br/>Default: `warn` |
+| `log_secrets` | `yes`<br/>`no` | Show or hide secrets in logs.<br/>Default: `no` (Hide) |
+| `log_format`  | `Proc`<br/>`String` | The name of a formatter or a lambda function that formats the log (see below).<br/>Default: `default`<br/>Alternative: `standard` |
+
+Option `logger` defines the destination of logs.
+
+#### `log_level` and `log_secrets`
 
 To increase debug level, use option `log_level` (e.g. using command line `--log-level=xx`, env var `ASCLI_LOG_LEVEL`, or an [Option Preset](#option-preset)).
 
 > [!NOTE]
-> When using the `direct` agent (`ascp`), additional transfer logs can be activated using `ascp` options and `ascp_args`, see [`direct`](#agent-direct).
+> When using the `direct` agent (`ascp`), additional transfer logs from `ascp` can be activated using `ascp` options and `ascp_args`, see [`direct`](#agent-direct).
 
 By default, passwords and secrets are redacted from logs.
 Set option `log_secrets` to `yes` to include secrets in logs.
 
-| Option        | Values | Description |
-|---------------|--------|-------------|
-| `logger`      | `stdout`<br/>`stderr`<br/>`syslog` | Type of output.<br/>Default: `stderr` |
-| `log_level`   | `trace2`<br/>`trace1`<br/>`debug`<br/>`info`<br/>`warn`<br/>`error` | Minimum level displayed.<br/>Default: `warn` |
-| `log_secrets` | `yes`<br/>`no` | Show or hide secrets in logs.<br/>Default: `no` (Hide) |
-| `log_format`  | `Proc`<br/>`String` | The name of a formatter or a lambda function that formats the log (see below).<br/>Default: `default`<br/>Alternative: `standard` |
+#### `log_format`
 
-Option `log_format` is typically set using `@ruby:`.
-It is a lambda that takes 4 arguments, see: [Ruby Formatter](https://github.com/ruby/logger/blob/master/lib/logger/formatter.rb) : `severity`, `time`, `progname`, `msg`.
+Option `log_format` support a few pre-defined formatters or a custom one using `@ruby:`.
+A customer formatter is a lambda that takes 4 arguments, see: [Ruby Formatter](https://github.com/ruby/logger/blob/master/lib/logger/formatter.rb) : `severity`, `time`, `progname`, `msg`.
 The default formatter is:
 
 ```ruby
-->(s, _d, _p, m){"#{s[0..2]} #{m}\n"}
+->(s, _d, _p, m){"#{s[0..2]}#{s[-1]} #{m}\n"}
 ```
 
-Availaible formatters for `log_format`:
+Available formatters for `log_format`:
 
-| Name      | Description                             |
-|-----------|-----------------------------------------|
-| `default` | Default formatter.                      |
-| `standard`| Standard Ruby formatter.                |
+| Name      | Description                                                                      |
+|-----------|----------------------------------------------------------------------------------|
+| `default` | Default formatter: Colorized 4 level level followed by message on the same line. |
+| `standard`| Standard Ruby formatter.                                                         |
+| `caller`  | Colorized 4 level level followed by caller, and then on next line: message.      |
+| `Proc`    | Custom lambda.                                                                   |
 
-Examples:
+#### Logging examples
 
 - Display debugging log on `stdout`:
 
@@ -3020,20 +3193,22 @@ To disable this warning, set the option `warn_insecure` to `no`.
 
 HTTP connection parameters (not `ascp` WSS) can be adjusted using option `http_options`:
 
-| Parameter                 | Type      | Default         | Handler   |
-|---------------------------|-----------|-----------------|-----------|
-| `read_timeout`            | `Integer` | `60`            | Ruby      |
-| `write_timeout`           | `Integer` | `60`            | Ruby      |
-| `open_timeout`            | `Integer` | `60`            | Ruby      |
-| `keep_alive_timeout`      | `Integer` | `2`             | Ruby      |
-| `ssl_options`             | `Array`   | See below       | Ruby      |
-| `user_agent`              | `Integer` | `ascli`       | `ascli` |
-| `download_partial_suffix` | `Integer` | `.http_partial` | `ascli` |
-| `retry_on_error`          | `Bool`    | `false`         | `ascli` |
-| `retry_on_timeout`        | `Bool`    | `true`          | `ascli` |
-| `retry_on_unavailable`    | `Bool`    | `true`          | `ascli` |
-| `retry_max`               | `Integer` | `1`             | `ascli` |
-| `retry_sleep`             | `Integer` | `4`             | `ascli` |
+| Parameter                 | Type      | Default         | Handler         |
+|-------------------------|---------|---------------|---------------|
+| `read_timeout`            | `Integer` | `60`            | Ruby            |
+| `write_timeout`           | `Integer` | `60`            | Ruby            |
+| `open_timeout`            | `Integer` | `60`            | Ruby            |
+| `keep_alive_timeout`      | `Integer` | `2`             | Ruby            |
+| `ssl_options`             | `Array`   | See below       | Ruby            |
+| `user_agent`              | `Integer` | `ascli`       | `ascli` Rest  |
+| `download_partial_suffix` | `Integer` | `.http_partial` | `ascli` Rest  |
+| `retry_on_error`          | `Bool`    | `false`         | `ascli` Rest  |
+| `retry_on_timeout`        | `Bool`    | `true`          | `ascli` Rest  |
+| `retry_on_unavailable`    | `Bool`    | `true`          | `ascli` Rest  |
+| `retry_max`               | `Integer` | `1`             | `ascli` Rest  |
+| `retry_sleep`             | `Integer` | `4`             | `ascli` Rest  |
+| `token_cache_max_age`     | `Integer` | `1800`          | `ascli` OAuth |
+| `token_refresh_threshold` | `Integer` | `120`           | `ascli` OAuth |
 
 Time values are in set **seconds** and can be of type either `Integer` or `Float`.
 Default values are the ones of Ruby:
@@ -3047,11 +3222,11 @@ Example:
 ascli aoc admin package list --http-options=@json:'{"read_timeout":10.0}'
 ```
 
-`ssl_options` corresponds to a list of options as listed in `man SSL_CTX_set_options`.
+The option `ssl_options` corresponds to a list of options as listed in `man SSL_CTX_set_options`.
 The default initial value is the default of Ruby as specified in `openssl/ssl.rb`.
 Each option can be specified as a `String` with the same name as in the OpenSSL library by removing the prefix: `SSL_OP_`, or an `Integer` (e.g. `0` resets to no option).
 If the name appears in the list, the option is set.
-If the name appears in the list prefixed with a hyphen (`-`), the option is unset.
+If the name appears in the list prefixed with a hyphen (`-`), the option is cleared.
 For example to enable option `SSL_OP_CIPHER_SERVER_PREFERENCE`, add it to the list as `CIPHER_SERVER_PREFERENCE`.
 To disable option `SSL_OP_SAFARI_ECDHE_ECDSA_BUG`, add it as `-SAFARI_ECDHE_ECDSA_BUG`.
 
@@ -3116,7 +3291,7 @@ ascli config proxy_check --fpac='function FindProxyForURL(url, host) {return "PR
 ```
 
 ```text
-PROXY proxy.example.com:1234;DIRECT
+PROXY proxy.example.com:8080;DIRECT
 ```
 
 ```shell
@@ -3175,11 +3350,6 @@ This is the reason why it is advised to install the Aspera Transfer Daemon durin
 
 By default, `ascli` uses the `ascp` binary found in **well known locations**, i.e. typical Aspera product installation paths.
 
-The way to specify the location of `ascp` is to use either options:
-
-- `ascp_path`
-- `use_product`
-
 The `config` plugin allows finding and specifying the location of `ascp`.
 It provides the following commands for `ascp` sub-command:
 
@@ -3188,32 +3358,11 @@ It provides the following commands for `ascp` sub-command:
 - `products` : list Aspera transfer products available locally
 - `connect` : list and download connect client versions available on internet
 
-#### Show path of currently used `ascp`
-
-```shell
-ascli config ascp show
-```
-
-```text
-/Users/laurent/.aspera/ascli/sdk/ascp
-```
-
-```shell
-ascli config ascp info
-```
-
-```text
-╭─────────┬──────────────────────────────────────────────────╮
-│ field   │ value                                            │
-╞═════════╪══════════════════════════════════════════════════╡
-│ ascp    │ /Users/john/.aspera/sdk/ascp                     │
-...
-╰─────────┴──────────────────────────────────────────────────╯
-```
-
 #### Selection of `ascp` location for [`direct`](#agent-direct) agent
 
-By default, `ascli` uses any found local product with `ascp`, including Transfer Daemon.
+Option: `ascp_path` is used to specify the location of `ascp`.
+The default value is: `product:FIRST`.
+By default, `ascli` uses any found local product with `ascp`, including Transfer Daemon (SDK).
 
 To override and use an alternate `ascp` path use option `ascp_path` (`--ascp-path=`)
 
@@ -3245,10 +3394,9 @@ Saved to default global preset global_common_defaults
 
 If the path has spaces, read section: [Shell and Command line parsing](#command-line-parsing-special-characters).
 
-If option `ascp_path` is not set, then the product identified with option `use_product` is used.
-
-If `use_product` is not set, then the first product found is used,
-this is equivalent to using option: `--use-product=FIRST`.
+A special value `product:<product name>` can be used for option `ascp_path`.
+It specifies to use `ascp` from the given product name.
+A special valuefor product name is `FIRST`, which means: use the first found.
 
 Locally installed Aspera products can be listed with:
 
@@ -3267,13 +3415,42 @@ ascli config ascp products list
 +---------------------------------------+----------------------------------------+
 ```
 
-Using the option `use_product` finds the `ascp` binary of the selected product.
-
 To permanently use the `ascp` of a product:
 
 ```shell
-ascli config ascp products use 'Aspera Connect'
-saved to default global preset /Users/laurent/Applications/Aspera Connect.app/Contents/Resources/ascp
+ascli config ascp products use 'IBM Aspera Connect'
+Updated: default: config <- global_common_defaults
+Updated: global_common_defaults: ascp_path <- product:IBM Aspera Connect
+Saving config file.
+```
+
+It is the same as executing:
+
+```shell
+ascli config preset set GLOBAL ascp_path 'product:IBM Aspera Connect'
+```
+
+To show the path of currently used `ascp`:
+
+```shell
+ascli config ascp show
+```
+
+```text
+/Users/laurent/.aspera/ascli/sdk/ascp
+```
+
+```shell
+ascli config ascp info
+```
+
+```text
+╭─────────┬──────────────────────────────────────────────────╮
+│ field   │ value                                            │
+╞═════════╪══════════════════════════════════════════════════╡
+│ ascp    │ /Users/john/.aspera/sdk/ascp                     │
+...
+╰─────────┴──────────────────────────────────────────────────╯
 ```
 
 #### Installation of Connect Client on command line
@@ -3326,8 +3503,8 @@ Transfers will be executed by a transfer client, here called **Transfer Agent**.
 
 The following agents are supported and selected with option `transfer`:
 
-| `transfer`                         | location | Description of agent          |
-|------------------------------------|----------|-------------------------------|
+| `transfer` | location | Description of agent          |
+|----------|----------|-------------------------------|
 | [`direct`](#agent-direct)          | local    | direct execution of `ascp`    |
 | [`transferd`](#agent-transfer-daemon) | local    | Aspera Transfer Daemon        |
 | [`connect`](#agent-connect-client) | local    | Aspera Connect Client         |
@@ -3354,14 +3531,16 @@ This is the default agent for `ascli` (option `--transfer=direct`).
 `ascli` will locally search installed Aspera products, including SDK, and use `ascp` from that component.
 Refer to section [FASP](#fasp-configuration).
 
+##### Agent: Direct: `transfer_info`
+
 The `transfer_info` option accepts the following optional parameters to control multi-session, Web Socket Session, Resume policy and add any argument to `ascp`:
 
-| Name                   | Type    | Description |
-|------------------------|---------|-------------|
+| Name                   | Type      | Description                                                                 |
+|------------------------|-----------|-----------------------------------------------------------------------------|
 | `wss`                  | `Bool`    | Web Socket Session<br/>Enable use of web socket session in case it is available<br/>Default: `true` |
 | `quiet`                | `Bool`    | If `true`, then `ascp` progress bar is not shown.<br/>Default: `false` |
 | `trusted_certs`        | `Array`   | List of repositories for trusted certificates. |
-| `client_ssh_key`       | `String` | SSH Keys to use for token-based transfers.<br/>One of: `dsa_rsa`, `rsa`, `per_client`.<br/>Default: `rsa` |
+| `client_ssh_key`       | `String`  | SSH Keys to use for token-based transfers.<br/>One of: `dsa_rsa`, `rsa`, `per_client`.<br/>Default: `rsa` |
 | `ascp_args`            | `Array`   | `Array` of strings with native `ascp` arguments.<br/>Default: `[]` |
 | `spawn_timeout_sec`    | `Float`   | Multi session<br/>Verification time that `ascp` is running<br/>Default: `3` |
 | `spawn_delay_sec`      | `Float`   | Multi session<br/>Delay between startup of sessions<br/>Default: `2` |
@@ -3380,14 +3559,26 @@ Sleep between iterations is given by the following formula where `iter_index` is
 max( sleep_max, sleep_initial * sleep_factor ^ iter_index )
 ```
 
-To display the native progress bar of `ascp`, use `--progress-bar=no --transfer-info=@json:'{"quiet":false}'`.
+To display the native progress bar of `ascp`, use:
+
+```shell
+--progress-bar=no --transfer-info=@json:'{"quiet":false}'`
+```
 
 To skip usage of management port (which disables custom progress bar), set option `monitor` to `false`.
-In that, use the native progress bar: `--transfer-info=@json:'{"monitor":false,"quiet":false}'`
+In that, use the native progress bar:
+
+```shell
+--transfer-info=@json:'{"monitor":false,"quiet":false}'`
+```
 
 By default, Ruby's root CA store is used to validate any HTTPS endpoint used by `ascp` (e.g. WSS).
 In order to use a custom certificate store, use the `trusted_certs` option of direct agent's option `transfer_info`.
-To use `ascp`'s default, use option: `--transfer-info=@json:'{"trusted_certs":null}'`.
+To use `ascp`'s default, use option:
+
+```shell
+--transfer-info=@json:'{"trusted_certs":null}'`.
+```
 
 Some transfer errors are considered **retry-able** (e.g. timeout) and some other not (e.g. wrong password).
 The list of known protocol errors and retry level can be listed:
@@ -3434,6 +3625,36 @@ In addition to standard methods described in section [File List](#list-of-files-
 > [!NOTE]
 > Those methods have limitations: they apply **only** to the [`direct`](#agent-direct) transfer agent (i.e. local `ascp`) and not for Aspera on Cloud.
 
+##### Agent: Direct: Management messages
+
+By default, `ascli` gets notification from `ascp` on its management port.
+This can be de-activated with parameter: `monitor=false` of `transfer_info`.
+
+It is also possible to send local messages to this management port.
+A typical use is to change the target rate of a running transfer.
+
+The communication is done through a flat JSON file that shall be created in `ascli` config folder as displayed with:
+
+```shell
+ascli config folder
+```
+
+The name of the file shall be: `send_<PID>`, where `<PID>` is the process id of the running `ascli`.
+
+If there is only one `ascli` running, one can get the PID like this:
+
+```shell
+ps -axo pid,command|grep ascli|grep -v grep|cut -f1 -d' '
+```
+
+Example to change the target rate:
+
+```shell
+echo '{"type":"RATE","Rate":300000}' > ~/.aspera/ascli/send_67470
+```
+
+When `ascli` detects this file, it uses it during a transfer and then deletes it.
+
 ##### Agent: Direct: `aspera.conf`: Virtual Links
 
 This agent supports a local configuration file: `aspera.conf` where Virtual links can be configured:
@@ -3610,11 +3831,11 @@ By specifying option: `--transfer=httpgw`, `ascli` will start transfers using th
 
 Parameters provided in option `transfer_info` are:
 
-| Name                | Type      | Description                           |
-|---------------------|-----------|---------------------------------------|
-| `url`               | `String`  | URL of the HTTP GW<br/>Mandatory |
+| Name                | Type      | Description                                               |
+|---------------------|-----------|-----------------------------------------------------------|
+| `url`               | `String`  | URL of the HTTP GW<br/>Mandatory                        |
 | `upload_chunk_size` | `Integer` | Size in bytes of chunks for upload<br/>Default: `64000` |
-| `api_version`       | `String`  | Force use of version (`v1`, `v2`)<br/>Default: `v2` |
+| `api_version`       | `String`  | Force use of version (`v1`, `v2`)<br/>Default: `v2`     |
 | `synchronous`       | `Bool`    | Wait for each message acknowledgment<br/>Default: `false` |
 
 Example:
@@ -3635,8 +3856,8 @@ Set option `transfer` to `transferd`.
 
 Options for `transfer_info` are:
 
-| Name     | Type     | Description |
-|----------|----------|-------------|
+| Name     | Type     | Description                                  |
+|----------|----------|----------------------------------------------|
 | `url`    | `String` | IP address and port listened by the daemon<br/>Mandatory<br/>Default: `:0` |
 | `start`  | `Bool`   | Start a new daemon.<br/>Default: `true` |
 | `stop`   | `Bool`   | Stop daemon when exiting `ascli`<br/>Default: `true` |
@@ -3672,7 +3893,7 @@ On Windows the compilation may fail for various reasons (3.1.1):
 
 - `cannot find -lx64-ucrt-ruby310`
 
-   &rarr; copy the file `[Ruby main dir]\lib\libx64-ucrt-ruby310.dll.a` to `[Ruby main dir]\lib\libx64-ucrt-ruby310.a` (remove the `dll` extension)
+   &rarr; copy the file `[Ruby main dir]\lib\libx64-ucrt-ruby310.dll.a` to (remove the `dll` extension) `[Ruby main dir]\lib\libx64-ucrt-ruby310.a`
   
 - `conflicting types for 'gettimeofday'`
 
@@ -3715,7 +3936,7 @@ The use of a [**transfer-spec**](#transfer-specification) instead of `ascp` comm
 - Common to all [Transfer Agent](#transfer-clients-agents)
 - Not dependent on command line limitations (special characters...)
 
-### Transfer Parameters
+#### Transfer Parameters
 
 All standard [**transfer-spec**](#transfer-specification) parameters can be specified.
 A [**transfer-spec**](#transfer-specification) can also be saved/overridden in the configuration file.
@@ -3747,8 +3968,10 @@ ascli config ascp schema transferd --format=jsonpp
 
 `ascp` argument or environment variable is provided in description.
 
+#### Transfer Specification Reference
+
 | ID | Name |
-| -- | ---- |
+|----|-----------|
 | A | Direct |
 | C | Connect |
 | D | Desktop |
@@ -3757,17 +3980,17 @@ ascli config ascp schema transferd --format=jsonpp
 | T | Transferd |
 
 | Field | Type | Description |
-| ----- | ---- | ----------- |
+|--------------------------------|---------|----------------------------------------------------------------------------------|
 | apply_local_docroot | boolean | Apply local docroot to source paths.<br/>(A, T)<br/>(`--apply-local-docroot`) |
 | authentication | string | Set to `token` for SSH bypass keys, else password asked if not provided.<br/>(C) |
 | cipher | string | In transit encryption algorithms.<br/>Allowed values: `none`, `aes-128`, `aes-192`, `aes-256`, `aes-128-cfb`, `aes-192-cfb`, `aes-256-cfb`, `aes-128-gcm`, `aes-192-gcm`, `aes-256-gcm`<br/>(`-c (conversion){enum}`) |
-| cipher_allowed | string | Returned by node API. Valid literals include `aes-128` and `none`.<br/>(C) |
-| content_protection | string | Enable client-side encryption at rest (CSEAR). (content protection)<br/>Allowed values: `encrypt`, `decrypt`<br/>(`--file-crypt={enum}`) |
-| content_protection_password | string | Specifies CSEAR password. (content protection)<br/>(env:`ASPERA_SCP_FILEPASS`) |
+| cipher_allowed | string | Returned by node API. Valid literals include `aes-128` and `none`.<br/>(C)<br/>Allowed values: `none`, `aes-128`, `aes-192`, `aes-256`, `aes-128-cfb`, `aes-192-cfb`, `aes-256-cfb`, `aes-128-gcm`, `aes-192-gcm`, `aes-256-gcm` |
+| content_protection | string | Enable client-side content protection (CSEAR, encryption-at-rest).<br/>For uploads, set to `encrypt` to transfer encrypted files and store them on the server with the extension `.aspera-env`. (`aspera.conf` parameter `transfer_encryption_content_protection_extension`). To download and decrypt encrypted files, set to `decrypt`<br/>`content_protection_password` must be specified if this option is set.<br/>Allowed values: `encrypt`, `decrypt`<br/>(`--file-crypt={enum}`) |
+| content_protection_password | string | Password for encryption/decryption of transferred assets.<br/>(env:`ASPERA_SCP_FILEPASS`) |
 | cookie | string | Metadata for transfer specified by application.<br/>(env:`ASPERA_SCP_COOKIE`) |
-| create_dir | boolean | Specifies whether to create new directories.<br/>(`-d`) |
+| create_dir | boolean | Create target directory if it doesn't already exist.<br/>If **all** the following conditions are met, then the `destination_root` specifies a filename instead of destination folder:<br/>- `create_dir` is `false`<br/>- A single source file is given on **command line**<br/>- The target folder specified by `destination_root` does not exist<br/>In all other cases, `destination_root` specifies a folder, and it is created if it does not already exist. I.e. if **any** of those conditions is met:<br/>- `create_dir` is `true`<br/>- Multiple source files are provided<br/>- List of source files are provided in a file (list or pair), default for Node API and `ascli`.<br/>- The target folder exists<br/>(`-d`) |
 | delete_before_transfer | boolean | Before transfer, delete files that exist at the destination but not at the source.<br/>The source and destination arguments must be directories that have matching names.<br/>Objects on the destination that have the same name but different type or size as objects on the source are not deleted.<br/>(`--delete-before-transfer`) |
-| delete_source | boolean | Remove transfered source files after transfer success. TODO equivalent to `remove_after_transfer` + `remove_empty_directories` + `remove_empty_source_directory`<br/>(A, N, T)<br/>(`--remove-after-transfer`) |
+| delete_source | boolean | Remove transfered source files after transfer success. Equivalent to `remove_after_transfer` + `remove_empty_directories` + `remove_empty_source_directory`. Take precedence over those.<br/>(A, N, T) |
 | destination_root | string | Destination root directory. |
 | destination_root_id | string | The file ID of the destination root directory.<br/>Required when using Bearer token auth for the destination node.<br/>(T) |
 | dgram_size | integer | UDP datagram size in bytes.<br/>(`-Z {integer}`) |
@@ -3783,16 +4006,16 @@ ascli config ascp schema transferd --format=jsonpp
 | https_fallback_port | integer | Specifies HTTPS port when cipher is used.<br/>(`-t {integer}`) |
 | icos | object | Configuration parameters for IBM Cloud Object Storage (ICOS).<br/>(T) |
 | keepalive | boolean | The session is running in persistent session mode.<br/>(A, T)<br/>(`--keepalive`) |
-| lock_min_rate | boolean | TODO: remove ?<br/>(C) |
+| lock_min_rate | boolean | n/a<br/>(C) |
 | lock_min_rate_kbps | boolean | If `true`, lock the minimum transfer rate to the value set for min_rate_kbps.<br/>If `false`, users can adjust the transfer rate up to the value set for target_rate_cap_kbps.<br/>(C, T) |
 | lock_rate_policy | boolean | If `true`, lock the rate policy to the default value.<br/>(C, T) |
-| lock_target_rate | boolean | TODO: remove ?<br/>(C) |
-| lock_target_rate_kbps | boolean | If `true`, lock the target transfer rate to the default value set for target_rate_kbps.<br/>If `false`, users can adjust the transfer rate up to the value set for target_rate_cap_kbps.<br/>(C, T) |
+| lock_target_rate | boolean | n/a<br/>(C) |
+| lock_target_rate_kbps | boolean | If `true`, lock the target transfer rate to the default value set for `target_rate_kbps`.<br/>If `false`, users can adjust the transfer rate up to the value set for `target_rate_cap_kbps`.<br/>(C, T) |
 | min_rate_cap_kbps | integer | The highest minimum rate that an incoming transfer can request, in kilobits per second.<br/>Client minimum rate requests that exceed the minimum rate cap are ignored.<br/>The default value of unlimited applies no cap to the minimum rate. (Default: 0)<br/>(C, T) |
 | min_rate_kbps | integer | Set the minimum transfer rate in kilobits per second.<br/>(`-m {integer}`) |
-| move_after_transfer | string | Move source files to the specified `archive-dir` directory after they are transferred correctly.<br/>Available as of 3.8.0. Details in ascp manual.<br/>Requires write permissions on the source.<br/>If `src_base` is specified, files are moved to `archive-dir`/`path-relative-to-srcbase`.<br/>`archive-dir` must be in the same file system (or cloud storage account) as the source files being transferred.<br/>`archive-dir` is subject to the same docroot restrictions as source files.<br/>`move_after_transfer` and `remove_after_transfer` are mutually exclusive options.<br/>After files have been moved to the archive, the original source directory structure is left in place. Empty directories are not saved to `archive-dir`. To remove empty source directories after a successful move operation, also set `remove_empty_directories` to `true`. When using `remove_empty_directories`, empty directory removal examination starts at the `srcbase` and proceeds down any subdirectories. If no `srcbase` is used and a file path (as opposed to a directory path) is specified, then only the immediate parent directory is examined and removed if it is empty following the move of the source file.<br/>(A, N, T)<br/>(`--move-after-transfer={string}`) |
-| multi_session | integer | Use multi-session transfer. max 128.<br/>Each participant on one host needs an independent UDP (-O) port.<br/>Large files are split between sessions only when transferring with `resume_policy`=`none`. |
-| multi_session_threshold | integer | Split files across multiple ascp sessions if their size in bytes is greater than or equal to the specified value.<br/>(0=no file is split)<br/>(A, N, T)<br/>(`--multi-session-threshold={integer}`) |
+| move_after_transfer | string | Move source files to the specified `archive-dir` directory after they are transferred correctly.<br/>Available as of 3.8.0. Details in `ascp` manual.<br/>Requires write permissions on the source.<br/>If `src_base` is specified, files are moved to `archive-dir`/`path-relative-to-srcbase`.<br/>`archive-dir` must be in the same file system (or cloud storage account) as the source files being transferred.<br/>`archive-dir` is subject to the same docroot restrictions as source files.<br/>`move_after_transfer` and `remove_after_transfer` are mutually exclusive options.<br/>After files have been moved to the archive, the original source directory structure is left in place. Empty directories are not saved to `archive-dir`. To remove empty source directories after a successful move operation, also set `remove_empty_directories` to `true`. When using `remove_empty_directories`, empty directory removal examination starts at the `srcbase` and proceeds down any subdirectories. If no `srcbase` is used and a file path (as opposed to a directory path) is specified, then only the immediate parent directory is examined and removed if it is empty following the move of the source file.<br/>(A, N, T)<br/>(`--move-after-transfer={string}`) |
+| multi_session | integer | Use multi-session transfer. max 128.<br/>Each participant on one host needs an independent UDP (-O) port.<br/>Large files are split between sessions only when transferring with `resume_policy`=`none`.<br/>(special:`-C {integer}`) |
+| multi_session_threshold | integer | Split files across multiple `ascp` sessions if their size in bytes is greater than or equal to the specified value.<br/>(0=no file is split)<br/>(A, N, T)<br/>(`--multi-session-threshold={integer}`) |
 | obfuscate_file_names | boolean | HTTP Gateway obfuscates file names when set to `true`.<br/>(H) |
 | overwrite | string | Overwrite files at the destination with source files of the same name based  on the policy:<br/>- `always` : Always overwrite the file.<br/>- `never` : Never overwrite the file. If the destination contains partial files that are older or the same  as the source files and resume is enabled, the partial files resume transfer. Partial files with checksums or sizes that differ from the source files  are not overwritten.<br/>- `diff` : (default) Overwrite the file if it is different from the source,  depending on the compare method (default is size). If the destination is object storage, `diff` has the same effect as always. If resume is not enabled, partial files are overwritten if they are different  from the source, otherwise they are skipped. If resume is enabled, only partial files with different sizes or checksums  from the source are overwritten; otherwise, files resume.<br/>- `diff+older` : Overwrite the file if it is older and different from the source,  depending on the compare method (default is size). If resume is not enabled, partial files are overwritten if they are older  and different from the source, otherwise they are skipped. If resume is enabled, only partial files that are different and older than  the source are overwritten, otherwise they are resumed.<br/>- `older` : Overwrite the file if its timestamp is older than the source timestamp.<br/>If you set an overwrite policy of `diff` or `diff+older`, difference is determined  by the value set for `resume_policy`:<br/>`none` : The source and destination files are always considered different and  the destination file is always overwritten<br/>`attributes` : The source and destination files are compared based on file attributes <br/>`sparse_checksum` : The source and destination files are compared based on sparse checksums, (currently file size)<br/>`full_checksum` : The source and destination files are compared based on full checksums<br/>Allowed values: `never`, `always`, `diff`, `older`, `diff+older`<br/>(`--overwrite={enum}`) |
 | password | string | Password for local Windows user when transfer user associated with node API user is not the same as the one running `asperanoded`.<br/>Allows impersonating the transfer user and have access to resources (e.g. network shares).<br/>Windows only, node API only.<br/>(N) |
@@ -3801,7 +4024,7 @@ ascli config ascp schema transferd --format=jsonpp
 | preserve_access_time | boolean | Preserve the source-file access timestamps at the destination.<br/>Because source access times are updated by the transfer operation, the timestamp that is preserved is the one just before to the transfer.<br/>(`--preserve-access-time`) |
 | preserve_acls | string | Preserve access control lists.<br/>(A, T)<br/>Allowed values: `none`, `native`, `metafile`<br/>(`--preserve-acls={enum}`) |
 | preserve_creation_time | boolean | Preserve source-file creation timestamps at the destination.<br/>Only Windows systems retain information about creation time. If the destination is not a Windows computer, this option is ignored.<br/>(`--preserve-creation-time`) |
-| preserve_extended_attrs | string | Preserve the extended attributes.<br/>(T, A)<br/>Allowed values: `none`, `native`, `metafile`<br/>(`--preserve-xattrs={enum}`) |
+| preserve_extended_attrs | string | Preserve the extended attributes.<br/>(A, T)<br/>Allowed values: `none`, `native`, `metafile`<br/>(`--preserve-xattrs={enum}`) |
 | preserve_file_owner_gid | boolean | Preserve the group ID for a file owner.<br/>(A, T)<br/>(`--preserve-file-owner-gid`) |
 | preserve_file_owner_uid | boolean | Preserve the user ID for a file owner.<br/>(A, T)<br/>(`--preserve-file-owner-uid`) |
 | preserve_modification_time | boolean | Set the modification time, the last time a file or directory was modified (written), of a transferred file to the modification of the source file or directory.<br/>Preserve source-file modification timestamps at the destination.<br/>(`--preserve-modification-time`) |
@@ -3830,9 +4053,9 @@ ascli config ascp schema transferd --format=jsonpp
 | source_root_id | string | The file ID of the source root directory. Required when using Bearer token auth for the source node.<br/>(N, T) |
 | src_base | string | Specify the prefix to be stripped off from each source object.<br/>The remaining portion of the source path is kept intact at the destination.<br/>Special care must be taken when used with cloud storage.<br/>(A, N, T)<br/>(`--src-base64=(conversion){string}`) |
 | src_base64 | string | The folder name below which the directory structure is preserved (base64 encoded).<br/>(A, T)<br/>(`--src-base64={string}`) |
-| ssh_args | array | Array of arguments to pass to SSH. Use with caution.<br/>(T, A)<br/>(`--ssh-args={array}`) |
+| ssh_args | array | Add arguments to the command-line arguments passed to the external ssh program (implies -SSH). The arguments are inserted before any key file(s) supplied to `ascp` and before the user/host arguments.<br/>(A, T)<br/>(special:`--ssh-arg={array}`) |
 | ssh_port | integer | Specifies SSH (TCP) port.<br/>(`-P {integer}`) |
-| ssh_private_key | string | Private key used for SSH authentication.<br/>Shall look like: -----BEGIN RSA PRIV4TE KEY-----\nMII...<br/>Note the JSON encoding: \n for newlines.<br/>(A, T)<br/>(env:`ASPERA_SCP_KEY`) |
+| ssh_private_key | string | Private key used for SSH authentication.<br/>Shall look like: -----BEGIN RSA PRIV4TE KEY-----&bsol;nMII...<br/>Note the JSON encoding: &bsol;n for newlines.<br/>(A, T)<br/>(env:`ASPERA_SCP_KEY`) |
 | ssh_private_key_passphrase | string | The passphrase associated with the transfer user's SSH private key. Available as of 3.7.2.<br/>(A, T)<br/>(env:`ASPERA_SCP_PASS`) |
 | ssh_private_key_path | string | Path to private key for SSH.<br/>(A, T)<br/>(`-i {string}`) |
 | sshfp | string | Check it against server SSH host key fingerprint.<br/>(`--check-sshfp={string}`) |
@@ -3843,10 +4066,10 @@ ascli config ascp schema transferd --format=jsonpp
 | target_rate_kbps | integer | Specifies desired speed for the transfer.<br/>(`-l {integer}`) |
 | title | string | Title of the transfer.<br/>(C, N, T) |
 | token | string | Authorization token. Type: Bearer, Basic or ATM. (Also arg -W)<br/>(env:`ASPERA_SCP_TOKEN`) |
-| use_ascp4 | boolean | Specify version of protocol. Do not use ascp4.<br/>(A, N, T) |
-| use_system_ssh | string | TODO, comment...<br/>(A, T)<br/>(`-SSH {string}`) |
-| wss_enabled | boolean | Server has Web Socket service enabled. |
-| wss_port | integer | TCP port used for websocket service feed. |
+| use_ascp4 | boolean | Specify version of protocol. Do not use `ascp4`.<br/>(A, N, T) |
+| use_system_ssh | boolean | Use an external `ssh` program instead of the built-in `libssh2` implementation to establish the connection to the remote host. The desired `ssh` program must be in the environment's `PATH`.<br/>To enable debugging of the `ssh` process, supply `-DD` and `--ssh-arg=-vv` arguments to `ascp`.<br/>(A, T)<br/>(`-SSH`) |
+| wss_enabled | boolean | Server has Web Socket service enabled.<br/>(special:`--ws-connect`) |
+| wss_port | integer | TCP port used for Web Socket service feed. |
 | xfer_max_retries | integer | Maximum number of retries, for node API initiated transfers. Shall not exceed aspera.conf `transfer_manager_max_retries` (default 5).<br/>(N) |
 
 #### Destination folder for transfers
@@ -3955,9 +4178,6 @@ Example: Source file `200KB.1` is renamed `sample1` on destination:
 ascli server upload --src-type=pair ~/Documents/Samples/200KB.1 /Upload/sample1
 ```
 
-> [!NOTE]
-> There are some specific rules to specify a file list when using **Aspera on Cloud**, refer to the AoC plugin section.
-
 #### Source directory structure on destination
 
 This section is not specific to `ascli` it is `ascp` behavior.
@@ -3981,18 +4201,18 @@ A leading `/` on destination is ignored (relative to docroot) unless docroot is
 
 In the following table source folder `d3` contains 2 files: `f1` and `d4/f2`.
 
-| Source files | Destination | Folders on Dest.  | `create_dir` | Destination Files           |
-|--------------|-------------|-------------------|--------------|-----------------------------|
-| `f1`         | `d/f`       | -                 | false        | Error: `d` does not exist.  |
-| `f1`         | `d/f`       | `d`               | false        | `d/f` (renamed)          |
-| `f1`         | `d/f/.`     | `d`               | false        | `d/f` (renamed)          |
-| `f1`         | `d/f`       | `d/f`             | false        | `d/f/f1`                    |
-| `f1` `f2`    | `d`         | `d`               | false        | `d/f1` `d/f2`               |
-| `d3`         | `d`         | -                 | false        | `d/f1` `d/f2` (renamed)    |
-| `f1`         | `d`         | -                 | true         | `d/f1`                      |
-| `f1` `f2`    | `d`         | -                 | true         | `d/f1` `d/f2`               |
-| `d1/f1` `d2/f2` | `d`      | -                 | true         | `d/f1` `d/f2`               |
-| `d3`         | `d`         | -                 | true         | `d/d3/f1` `d/d3/d4/f2`      |
+| Source files    | Destination | Folders on Dest.  | `create_dir` | Destination Files           |
+|-----------------|-----|-----|------|-----------------------------------|
+| `f1`            | `d/f`       | -                 | false        | Error: `d` does not exist.  |
+| `f1`            | `d/f`       | `d`               | false        | `d/f` (renamed)             |
+| `f1`            | `d/f/.`     | `d`               | false        | `d/f` (renamed)             |
+| `f1`            | `d/f`       | `d/f`             | false        | `d/f/f1`                    |
+| `f1` `f2`       | `d`         | `d`               | false        | `d/f1` `d/f2`               |
+| `d3`            | `d`         | -                 | false        | `d/f1` `d/f2` (renamed)     |
+| `f1`            | `d`         | -                 | true         | `d/f1`                      |
+| `f1` `f2`       | `d`         | -                 | true         | `d/f1` `d/f2`               |
+| `d1/f1` `d2/f2` | `d`         | -                 | true         | `d/f1` `d/f2`               |
+| `d3`            | `d`         | -                 | true         | `d/d3/f1` `d/d3/d4/f2`      |
 
 If a file par list is provided then it is possible to rename or specify a different destination folder for each source (relative to the destination).
 
@@ -4043,8 +4263,13 @@ When multi-session is used, one separate UDP port is used per session (refer to
 
 #### Content protection
 
-Also known as Client-side encryption at rest (CSEAR), content protection allows a client to send files to a server which will store them encrypted (upload), and decrypt files as they are being downloaded from a server, both using a passphrase, only known by users sharing files.
-Files stay encrypted on server side.
+Content protection (Client-Side Encryption at Rest, CSEAR)) ensures that files remain encrypted while stored on the server.
+With CSEAR, the client encrypts files during upload and decrypts files during download, using a passphrase known only to the users sharing the files.
+
+- Upload: Files are encrypted on the client side before being sent to the server.
+- Download: Files are decrypted on the client side as they are retrieved from the server.
+
+At all times, files remain encrypted on the server; encryption and decryption occur exclusively on the client side.
 
 Activating CSEAR consists in using transfer spec parameters:
 
@@ -4057,6 +4282,11 @@ Example: parameter to download a Faspex package and decrypt on the fly
 --ts=@json:'{"content_protection":"decrypt","content_protection_password":"my_password_here"}'
 ```
 
+> [!NOTE]
+> Faspex 5 requires package parameter `ear_enabled` set to `true` for CSEAR.
+> In that case the transfer spec parameter `content_protection` is automatically set.
+> `content_protection_password` is then required in all cases.
+
 #### Transfer Spec Examples
 
 - Change target rate
@@ -4102,7 +4332,7 @@ It can be configured:
 
 - Using utility [`schtasks.exe`](https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/schtasks-create)
 
-- Using Powershell function [`scheduletasks`](https://learn.microsoft.com/en-us/powershell/module/scheduledtasks)
+- Using PowerShell function [`scheduletasks`](https://learn.microsoft.com/en-us/powershell/module/scheduledtasks)
 
 - Using `taskschd.msc` (UI)
 
@@ -4306,14 +4536,14 @@ where:
 - `dirname` is the folder name and can contain `/` to specify a subfolder.
 - Supported arguments are:
 
-| Name     | Type  | Description |
-|----------|-------|-------------|
-| count    | int   | Number of files<br/>Mandatory |
-| file     | string| Basename for files<br/>Default: `file` |
-| size     | int   | Size of first file.<br/>Default: 0 |
-| inc      | int   | Increment applied to determine next file size<br/>Default: 0 |
-| seq      | enum  | Sequence in determining next file size<br/>Values: `random`, `sequential`<br/>Default: `sequential` |
-| buf_init | enum  | How source data is initialized<br/>Option `none` is not allowed for downloads.<br/>Values:`none`, `zero`, `random`<br/>Default:`zero` |
+| Name     | Type   | Description                                                    |
+|----------|--------|----------------------------------------------------------------|
+| count    | int    | Number of files<br/>Mandatory |
+| file     | string | Basename for files<br/>Default: `file` |
+| size     | int    | Size of first file.<br/>Default: 0 |
+| inc      | int    | Increment applied to determine next file size<br/>Default: 0 |
+| seq      | enum   | Sequence in determining next file size<br/>Values: `random`, `sequential`<br/>Default: `sequential` |
+| buf_init | enum   | How source data is initialized<br/>Option `none` is not allowed for downloads.<br/>Values:`none`, `zero`, `random`<br/>Default:`zero` |
 
 The sequence parameter is applied as follows:
 
@@ -4365,7 +4595,7 @@ ascli server upload "faux:///mydir?file=testfile&count=1000&size=1" --to-folder=
 ```text
 ascli -h
 NAME
-        ascli -- a command line tool for Aspera Applications (v4.24.1)
+        ascli -- a command line tool for Aspera Applications (v4.25.0.pre)
 
 SYNOPSIS
         ascli COMMANDS [OPTIONS] [ARGS]
@@ -4387,7 +4617,7 @@ COMMANDS
 OPTIONS
         Options begin with a '-' (minus), and value is provided on command line.
         Special values are supported beginning with special prefix @pfx:, where pfx is one of:
-        val, base64, csvt, env, file, uri, json, lines, list, none, path, re, ruby, secret, stdin, stdbin, yaml, zlib, extend, preset, vault
+        val, base64, csvt, env, file, uri, json, lines, list, none, path, re, ruby, secret, stdin, stdbin, yaml, zlib, extend, preset, vault, 
         Dates format is 'DD-MM-YY HH:MM:SS', or 'now' or '-<num>h'
 
 ARGS
@@ -4396,11 +4626,10 @@ ARGS
 OPTIONS: global
         --interactive=ENUM           Use interactive input of missing params: [no], yes
         --ask-options=ENUM           Ask even optional options: [no], yes
-        --struct-parser=ENUM         Default parser when expected value is a struct: json, ruby
         --format=ENUM                Output format: text, nagios, ruby, json, jsonpp, yaml, [table], csv, image
-        --output=VALUE               Destination for results (String)
+        --output=VALUE               Destination for results
         --display=ENUM               Output only some information: [info], data, error
-        --fields=VALUE               Comma separated list of: fields, or ALL, or DEF (String, Array, Regexp, Proc)
+        --fields=VALUE               Comma separated list of: fields, or ALL, or DEF (Array, Regexp, Proc)
         --select=VALUE               Select only some items in lists: column, value (Hash, Proc)
         --table-style=VALUE          (Table) Display style (Hash)
         --flat-hash=ENUM             (Table) Display deep values as additional keys: no, [yes]
@@ -4414,14 +4643,16 @@ OPTIONS: global
         --ui=ENUM                    Method to start browser: text, [graphical]
         --invalid-characters=VALUE   Replacement character and invalid filename characters
         --log-level=ENUM             Log level: trace2, trace1, debug, info, [warn], error, fatal, unknown
-        --log-format=VALUE           Log formatter (Proc, Logger::Formatter, String)
+        --log-format=VALUE           Log formatter (Proc, Logger::Formatter)
         --logger=ENUM                Logging method: [stderr], stdout, syslog
         --lock-port=VALUE            Prevent dual execution of a command, e.g. in cron (Integer)
         --once-only=ENUM             Process only new items (some commands): [no], yes
         --log-secrets=ENUM           Show passwords in logs: [no], yes
         --clean-temp=ENUM            Cleanup temporary files on exit: no, [yes]
-        --pid-file=VALUE             Write process identifier to file, delete on exit (String)
-        --home=VALUE                 Home folder for tool (String)
+        --temp-folder=VALUE          Temporary folder
+        --pid-file=VALUE             Write process identifier to file, delete on exit
+        --parser=ENUM                Default parser for structured parameters and options: none, json, ruby, yaml
+        --home=VALUE                 Home folder for tool
         --config-file=VALUE          Path to YAML file with preset configuration
         --secret=VALUE               Secret for access keys
         --vault=VALUE                Vault for secrets (Hash)
@@ -4432,17 +4663,15 @@ OPTIONS: global
         --bfail=ENUM                 Bulk operation error handling: no, [yes]
     -N, --no-default                 Do not load default configuration for plugin
     -P, --presetVALUE                Load the named option preset from current config file
-        --version-check-days=VALUE   Period in days to check new version (zero to disable)
+        --version-check-days=VALUE   Period in days to check new version (zero to disable) (Integer)
         --plugin-folder=VALUE        Folder where to find additional plugins
         --override=ENUM              Wizard: override existing value: [no], yes
         --default=ENUM               Wizard: set as default configuration for specified plugin (also: update): no, [yes]
-        --test-mode=ENUM             Wizard: skip private key check step: [no], yes
         --key-path=VALUE             Wizard: path to private key for JWT
-        --ascp-path=VALUE            Ascp: Path to ascp
-        --use-product=VALUE          Ascp: Use ascp from specified product
         --sdk-url=VALUE              Ascp: URL to get Aspera Transfer Executables
-        --locations-url=VALUE        Ascp: URL to get locations of Aspera Transfer Daemon
-        --sdk-folder=VALUE           Ascp: SDK folder path
+        --ascp-path=VALUE            Ascp: Path to ascp (or product with "product:")
+        --locations-url=VALUE        Ascp: URL to get download locations of Aspera Transfer Daemon
+        --sdk-folder=VALUE           Ascp: SDK installation folder path
         --progress-bar=ENUM          Display progress bar: [no], yes
         --smtp=VALUE                 Email: SMTP configuration (Hash)
         --notify-to=VALUE            Email: Recipient for notification of transfers
@@ -4450,9 +4679,9 @@ OPTIONS: global
         --insecure=ENUM              HTTP/S: Do not validate any certificate: [no], yes
         --ignore-certificate=VALUE   HTTP/S: Do not validate certificate for these URLs (Array)
         --warn-insecure=ENUM         HTTP/S: Issue a warning if certificate is ignored: no, [yes]
-        --cert-stores=VALUE          HTTP/S: List of folder with trusted certificates (Array, String)
+        --cert-stores=VALUE          HTTP/S: List of folder with trusted certificates (Array)
         --http-options=VALUE         HTTP/S: Options for HTTP/S socket (Hash)
-        --http-proxy=VALUE           HTTP/S: URL for proxy with optional credentials (String)
+        --http-proxy=VALUE           HTTP/S: URL for proxy with optional credentials
         --cache-tokens=ENUM          Save and reuse OAuth tokens: no, [yes]
         --fpac=VALUE                 Proxy auto configuration script
         --proxy-credentials=VALUE    HTTP proxy credentials for fpac: user, password (Array)
@@ -4464,7 +4693,7 @@ OPTIONS: global
         --transfer-info=VALUE        Parameters for transfer agent (Hash)
 
 COMMAND: config
-SUBCOMMANDS: ascp check_update coffee detect documentation download echo email_test file folder gem genkey image initdemo open platform plugins preset proxy_check pubkey remote_certificate smtp_settings test tokens transferd vault wizard
+SUBCOMMANDS: ascp check_update coffee detect documentation download echo email_test file folder gem genkey image initdemo open platform plugins preset proxy_check pubkey remote_certificate smtp_settings sync test tokens transferd vault wizard
 
 
 COMMAND: shares
@@ -4476,7 +4705,7 @@ OPTIONS:
 
 
 COMMAND: node
-SUBCOMMANDS: access_keys api_details asperabrowser async basic_token bearer_token browse cat central delete download events health info license mkdir mkfile mklink rename search service simulator slash space ssync stream sync telemetry transfer transport upload watch_folder
+SUBCOMMANDS: access_keys api_details asperabrowser async basic_token bearer_token browse cat central delete download events health info license mkdir mkfile mklink rename search service simulator slash space spec ssync stream sync telemetry transfer transport upload watch_folder
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
@@ -4502,7 +4731,7 @@ OPTIONS:
 
 
 COMMAND: orchestrator
-SUBCOMMANDS: health info plugins processes workflow
+SUBCOMMANDS: health info monitors plugins processes workflows workorders workstep
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
@@ -4528,7 +4757,6 @@ OPTIONS:
         --instance=VALUE             ATS instance in ibm cloud
         --ats-key=VALUE              ATS key identifier (ats_xxx)
         --ats-secret=VALUE           ATS key secret
-        --params=VALUE               Parameters access key creation (@json:)
         --cloud=VALUE                Cloud provider
         --region=VALUE               Cloud region
 
@@ -4539,12 +4767,13 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
         --password=VALUE             User's password
+        --auth=ENUM                  OAuth type of authentication: web, [jwt], boot
         --client-id=VALUE            OAuth client identifier
         --client-secret=VALUE        OAuth client secret
-        --redirect-uri=VALUE         OAuth redirect URI for web authentication
-        --auth=ENUM                  OAuth type of authentication: web, [jwt], boot
-        --private-key=VALUE          OAuth JWT RSA private key PEM value (prefix file path with @file:)
-        --passphrase=VALUE           OAuth JWT RSA private key passphrase
+        --redirect-uri=VALUE         OAuth (Web) redirect URI for web authentication
+        --private-key=VALUE          OAuth (JWT) RSA private key PEM value (prefix file path with @file:)
+        --passphrase=VALUE           OAuth (JWT) RSA private key passphrase
+        --scope=VALUE                OAuth scope for API calls
         --box=VALUE                  Package inbox, either shared inbox name or one of: inbox, inbox_history, inbox_all, inbox_all_history, outbox, outbox_history, pending, pending_history, all or ALL
         --shared-folder=VALUE        Send package with files from shared folder
         --group-type=ENUM            Type of shared box: [shared_inboxes], workgroups
@@ -4588,12 +4817,11 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
         --password=VALUE             User's password
-        --skip-format=ENUM           Skip this preview format (multiple possible): png, mp4
+        --skip-format=ENUM           Skip this preview format: png, mp4
         --folder-reset-cache=ENUM    Force detection of generated preview by refresh cache: [no], header, read
-        --skip-types=VALUE           Skip types in comma separated list
+        --skip-types=VALUE           Skip generation for those types of files (Array)
         --previews-folder=VALUE      Preview folder in storage root
-        --temp-folder=VALUE          Path to temp folder
-        --skip-folders=VALUE         List of folder to skip
+        --skip-folders=VALUE         List of folder to skip (Array)
         --base=VALUE                 Basename of output for for test
         --scan-path=VALUE            Subpath in folder id to start scan in (default=/)
         --scan-id=VALUE              Folder id in storage to start scan in, default is access key main folder id
@@ -4624,17 +4852,17 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
         --password=VALUE             User's password
-        --auth=ENUM                  OAuth type of authentication: web, [jwt]
-        --client-id=VALUE            OAuth API client identifier
-        --client-secret=VALUE        OAuth API client secret
-        --scope=VALUE                OAuth scope for AoC API calls
-        --redirect-uri=VALUE         OAuth API client redirect URI
-        --private-key=VALUE          OAuth JWT RSA private key PEM value (prefix file path with @file:)
-        --passphrase=VALUE           RSA private key passphrase (String)
-        --workspace=VALUE            Name of workspace (String, NilClass)
+        --auth=ENUM                  OAuth type of authentication: web, [jwt], boot
+        --client-id=VALUE            OAuth client identifier
+        --client-secret=VALUE        OAuth client secret
+        --redirect-uri=VALUE         OAuth (Web) redirect URI for web authentication
+        --private-key=VALUE          OAuth (JWT) RSA private key PEM value (prefix file path with @file:)
+        --passphrase=VALUE           OAuth (JWT) RSA private key passphrase
+        --scope=VALUE                OAuth scope for API calls
+        --workspace=VALUE            Name of workspace
         --new-user-option=VALUE      New user creation option for unknown package recipients (Hash)
         --validate-metadata=ENUM     Validate shared inbox metadata: no, [yes]
-        --package-folder=VALUE       Field of package to use as folder name, or @none: (String, NilClass)
+        --package-folder=VALUE       Field of package to use as folder name, or @none:
 
 
 COMMAND: server
@@ -4643,7 +4871,7 @@ OPTIONS:
         --url=VALUE                  URL of application, e.g. https://app.example.com/aspera/app
         --username=VALUE             User's identifier
         --password=VALUE             User's password
-        --ssh-keys=VALUE             SSH key path list (Array or single)
+        --ssh-keys=VALUE             SSH key path list (Array)
         --passphrase=VALUE           SSH private key passphrase
         --ssh-options=VALUE          SSH options (Hash)
 
@@ -4670,18 +4898,17 @@ This option is available only for some resources: if you need it: try and see if
 ### Option: `query`
 
 The `query` option can generally be used to add URL parameters to commands that list resources.
-It takes either a `Hash` or an `Array`, corresponding to key/value pairs that appear in the query part of request.
+It takes either a `Hash`, corresponding to key/value pairs that appear in the query part of request.
 
 For example: `--query=@json:'{"p1":"v1","p2":"v2"}'` leads to query: `?p1=v1&p2=v2`.
 
-If the same parameter needs to be provided several times, then it's possible as well to provide an `Array` or 2-element `Array`: `--query=@json:'[["p1":,"v1"],["p2":"v2"]]'` leads to the same result as previously.
+If the same parameter needs to be provided several times, then it's possible as well to provide an `Array`.
 
-If PHP's style array is used, then one can use either:
+For example: `--query=@json:'{"p":["v1","v2"]}'` leads to query: `?p=v1&p=v2`.
 
-- `--query=@json:'{"a":["[]","v1","v2"]}'`
-- `--query=@json:'[["a[]","v1"],["a[]","v2"]]'`
+If PHP's style array is expected in the API, then just add `[]` to the name of the parameter.
 
-Both result in: `?a[]=v1&a[]=v2`.
+For example: `--query=@json:'{"p[]":["v1","v2"]}'` leads to query: `?p[]=v1&p[]=v2`.
 
 ### Plugins
 
@@ -4748,39 +4975,50 @@ Aspera on Cloud API requires the use of OAuth v2 mechanism for authentication (H
 
 It is recommended to use the wizard to set it up, although manual configuration is also possible.
 
-### Configuration: Using Wizard
+### AoC configuration: Using Wizard
 
 `ascli` provides a configuration [wizard](#wizard).
 
 The wizard guides you through the steps to create a new configuration preset for Aspera on Cloud.
 
-The first optional argument is the URL of your Aspera on Cloud instance, e.g. `https://_your_instance_.ibmaspera.com` or simply the organization name, and a second optional argument can also be provided to specify the plugin name, e.g. `aoc` for Aspera on Cloud.
+The first optional argument is the URL of your Aspera on Cloud instance or simply the organization name, i.e. one of those :
+
+- `_your_organization_`
+- `_your_organization_.ibmaspera.com`
+- `https://_your_organization_.ibmaspera.com`
+
+The second optional argument can also be provided to specify the plugin name, e.g. `aoc` for Aspera on Cloud.
 If optional arguments are not provided, the wizard will ask interactively and try to detect the application.
 
 Here is a sample invocation :
 
-```text
-ascli config wizard
-option: url> https://_your_instance_.ibmaspera.com
-Detected: Aspera on Cloud
-Preparing preset: aoc_myorg
-Please provide path to your private RSA key, or empty to generate one:
+```console
+$ ascli config wizard
+Using: Aspera on Cloud at https://_my_org_.ibmaspera.com
+Path to private RSA key (leave empty to generate):
 option: key_path>
-using existing key:
-/Users/myself/.aspera/ascli/aspera_aoc_key
+Using existing key:
+/home/john/.aspera/ascli/my_private_key.pem
+Please Log in as user laurent.martin.aspera@fr.ibm.com at: https://_my_org_.ibmaspera.com
+Navigate to: (User) → Account Settings → Profile → Public Key
+Check or update the value to (including BEGIN/END lines):
+-----BEGIN PUBLIC KEY-----
+MIICIjANBg....
+....
+....kCAwEAAQ==
+-----END PUBLIC KEY-----
+Once updated or validated, press [Enter].
+
 Using global client_id.
-option: username> john@example.com
-Updating profile with new key
-creating new config preset: aoc_myorg
-Setting config preset as default for aspera
-saving configuration file
-Done.
+Preparing preset: aoc_my_org_ibmaspera_com_john_example_com
+Setting config preset as default for aoc
 You can test with:
 ascli aoc user profile show
+Saving config file.
 ```
 
 > [!NOTE]
-> In above example, replace `https://_your_instance_.ibmaspera.com` with your actual AoC URL.
+> In above example, replace `https://_my_org_.ibmaspera.com` with your actual AoC URL.
 
 Optionally, it is possible to create a new organization-specific integration, i.e. client application identification.
 For this, specify the option: `--use-generic-client=no`.
@@ -4788,11 +5026,11 @@ For this, specify the option: `--use-generic-client=no`.
 If you already know the application, and want to limit the detection to it, provide URL and plugin name:
 
 ```shell
-ascli config wizard _your_instance_ aoc
+ascli config wizard _my_org_ aoc
 ```
 
 > [!NOTE]
-> In above example, replace `_your_instance_` with the first part of your actual AoC URL: `https://_your_instance_.ibmaspera.com`.
+> In above example, replace `_my_org_` with the first part of your actual AoC URL: `https://_my_org_.ibmaspera.com`.
 
 After successful completion of the wizard, a new configuration preset is created, and set as default for the `aoc` plugin.
 This can be verified with command:
@@ -4801,12 +5039,12 @@ This can be verified with command:
 ascli config preset over
 ```
 
-### Configuration: Using manual setup
+### AoC configuration: Using manual setup
 
 > [!NOTE]
 > If you used the wizard (recommended): skip this section.
 
-#### Configuration details
+#### AoC manual configuration: Details
 
 Several types of OAuth authentication are supported:
 
@@ -4836,7 +5074,7 @@ Else you can use a specific OAuth API `client_id`, the first step is to declare
 
 Let's start by a registration with web based authentication (auth=web):
 
-- Open a web browser, log to your instance: e.g. `https://_your_instance_.ibmaspera.com/`
+- Open a web browser, log to your instance: e.g. `https://_my_org_.ibmaspera.com/`
   (use your actual AoC instance URL)
 - Go to Apps &rarr; Admin &rarr; Organization &rarr; Integrations
 - Click **Create New**
@@ -4861,14 +5099,14 @@ Let's create an [Option Preset](#option-preset) called: `my_aoc_org` using `ask`
 
 ```shell
 ascli config preset ask my_aoc_org url client_id client_secret
-option: url> https://_your_instance_.ibmaspera.com/
+option: url> https://_my_org_.ibmaspera.com/
 option: client_id> my_client_id_here
 option: client_secret> my_client_secret_here
 updated: my_aoc_org
 ```
 
 > [!NOTE]
-> In above example, replace `https://_your_instance_.ibmaspera.com` with your actual AoC URL.
+> In above example, replace `https://_my_org_.ibmaspera.com` with your actual AoC URL.
 
 (This can also be done in one line using the command `config preset update my_aoc_org --url=...`)
 
@@ -4896,7 +5134,7 @@ This can be done in two manners:
 
 - Graphically
 
-  - Open a web browser, log to your instance: `https://_your_instance_.ibmaspera.com/`
+  - Open a web browser, log to your instance: `https://_my_org_.ibmaspera.com/`
     (Use your actual AoC instance URL)
   - Go to Apps &rarr; Admin &rarr; Organization &rarr; Integrations
   - Click on the previously created application
@@ -4939,7 +5177,7 @@ This can be done in two manners:
 
 Open the previously generated public key located here: `$HOME/.aspera/ascli/my_private_key.pub`
 
-- Open a web browser, log to your instance: `https://_your_instance_.ibmaspera.com/`
+- Open a web browser, log to your instance: `https://_my_org_.ibmaspera.com/`
   (Use your actual AoC instance URL)
 - Click on the user's icon (top right)
 - Select **Account Settings**
@@ -5039,7 +5277,7 @@ ascli aoc files bearer_token_node /
 ```
 
 ```shell
-ascli aoc admin node v4 1234 --secret=_ak_secret_here_ bearer_token_node /
+ascli aoc admin node v4 <node_id> --secret=_ak_secret_here_ bearer_token_node /
 ```
 
 ### Administration
@@ -5623,7 +5861,7 @@ ascli aoc packages shared_inboxes list
 
 Use fields: `recipients` and/or `bcc_recipients` to provide the list of recipients: **user** or **shared inbox**:
 
-- Provide either IDs as expected by API: `"recipients":[{"type":"dropbox","id":"1234"}]`
+- Provide either IDs as expected by API: `"recipients":[{"type":"dropbox","id":"_my_shibox_id_"}]`
 - or just names: `"recipients":[{"The Dest"}]`.
 
 ascli will resolve the list of email addresses and dropbox names to the expected type/ID list, based on case-insensitive partial match.
@@ -5642,13 +5880,13 @@ ascli aoc packages send @json:'{"name":"my title","note":"my note","recipients":
 ##### Example: Send a package to a shared inbox with metadata
 
 ```shell
-ascli aoc packages send --workspace="my ws" @json:'{"name":"my pack title","recipients":["Shared Inbox With Meta"],"metadata":{"Project Id":"123","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' ~/Documents/Samples/200KB.1
+ascli aoc packages send --workspace="<workspace_name>" @json:'{"name":"my pack title","recipients":["Shared Inbox With Meta"],"metadata":{"Project Id":"123","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' ~/Documents/Samples/200KB.1
 ```
 
 It is also possible to use identifiers and API parameters:
 
 ```shell
-ascli aoc packages send --workspace="my ws" @json:'{"name":"my pack title","recipients":[{"type":"dropbox","id":"12345"}],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' ~/Documents/Samples/200KB.1
+ascli aoc packages send --workspace="<workspace_name>" @json:'{"name":"my pack title","recipients":[{"type":"dropbox","id":"12345"}],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' ~/Documents/Samples/200KB.1
 ```
 
 ##### Example: Send a package with files from the Files app
@@ -5693,12 +5931,12 @@ By default, all files in the package are downloaded, i.e. `.` is used as the fil
 Option `package_folder` defines the attribute of folder used as destination sub folder in the `to_folder` path (see description earlier).
 The following syntax is supported
 
-| Syntax | Description |
-|--------|-------------|
-| `@none:` | No subfolder is created, files are downloaded directly into the specified `to_folder`. |
-| `<field>` | A subfolder named after the package's specified field is created inside `to_folder`. |
-| `<field1>+<field2>` | A subfolder named after the combination of two package fields with a `.` is created inside `to_folder`. |
-| `<field1>+<field2>?` | A subfolder named after the package's specified field1 is created, unless it already exists. Else it falls back to the combination of both fields with `.`. |
+| Syntax               | Description                                                                            |
+|----------------------|----------------------------------------------------------------------------------------|
+| `@none:`             | No subfolder is created, files are downloaded directly into the specified `to_folder`. |
+| `<field>`            | A subfolder named after the package's specified field is created inside `to_folder`.   |
+| `<field1>+<field2>`  | A subfolder named after the combination of two package fields with a `.` is created inside `to_folder`. |
+| `<field1>+<field2>?` | A subfolder named after the package's specified field1 is created, unless it already exists.<br/>Else it falls back to the combination of both fields with `.`. |
 
 The special value `seq` for `<field2>` will append an incrementing number to the folder name starting at `1`.
 If `?` is used, then the sequence number is used only if the folder already exists.
@@ -5768,15 +6006,15 @@ ascli aoc package node_info <package ID here> / --format=json --show-secrets=yes
 
 By default, when using `aoc packages list` or `aoc packages receive ALL`, the following `query` is performed:
 
-| Query parameter            | Value   |
-|----------------------------|---------|
+| Query parameter            | Value                                         |
+|----------------------------|-----------------------------------------------|
 | `archived`                 | `false` |
 | `has_content`              | `true`  |
 | `received`                 | `true`  |
 | `completed`                | `true`  |
-| `workspace_id`             | Set based on current workspace. |
+| `workspace_id`             | Set based on current workspace.               |
 | `dropbox_id`               | Set according to `dropbox_name`, if provided. |
-| `exclude_dropbox_packages` | `true` unless `dropbox_id` is provided. |
+| `exclude_dropbox_packages` | `true` unless `dropbox_id` is provided.       |
 
 Parameters provided using option `query` override this query.
 To remove a parameter, set it to `null`.
@@ -5839,7 +6077,7 @@ ascli aoc files download <single file path>
 
 #### Shared folders
 
-Like in AoC web UI, "Shared Folders" can be created and shared with either **Private** or **Public** links.
+Like in AoC web UI, **Shared Folders** can be created and shared with either **Private** or **Public** links.
 **Private** links require the collaborator to log in to access the shared folder.
 **Public** links include a passcode that enables the user to access the shared folder without login-in.
 
@@ -5866,19 +6104,19 @@ The basic payload to create a permission, i.e. a Shared Folder (last argument at
 `ascli` expects the same payload for creation.
 `ascli` automatically populates some payload fields and provides convenient additional fields that generate native fields:
 
-| Field           | Type     | Description |
-|-----------------|----------|-------------|
+| Field           | Type     | Description                                                          |
+|-----------------|----------|----------------------------------------------------------------------|
 | `file_id`       | Native<br/>Auto     | ID of the folder to share, as specified in the command line by path. |
-| `access_levels` | Native<br/>Optional | List of access levels to set for the shared folder. Defaults to full access. |
+| `access_levels` | Native<br/>Optional | List of access levels to set for the shared folder.<br/>Defaults to full access. |
 | `tags`          | Native<br/>Auto     | Set with expected values for AoC: username who creates, and workspace in which the shared folder is created. |
-| `access_type`   | Native<br/>Required | Type of access, such as `user`, `group`, or `workspace`. Can be set with parameter `with`. |
+| `access_type`   | Native<br/>Required | Type of access, such as `user`, `group`, or `workspace`.<br/>Can be set with parameter `with`. |
 | `access_id`     | Native<br/>Required | ID of the user, group, or workspace (see `with`) |
-| `with`          | `ascli`           | Recipient of shared folder. Can be a username, a group name, or a workspace name. `ascli` will resolve the name to the proper type and ID in fields `access_type` and `access_id`. If the value is the empty string, then it declares the shared folder in the workspace (first action to do, see below). |
+| `with`          | `ascli`           | Recipient of shared folder. Can be a username, a group name, or a workspace name.<br/>`ascli` will resolve the name to the proper type and ID in fields `access_type` and `access_id`.<br/>If the value is the empty string, then it declares the shared folder in the workspace (first action to do, see below). |
 | `link_name`     |  `ascli`          | Name of the link file created in the user's home folder for private links. |
 | `as`            |  `ascli`          | Name of the link file created in the user's home folder for admin shared folders. |
 
-In order to declare/create the shared folder in the workspace, a special value for `access_id` is used: `ASPERA_ACCESS_KEY_ADMIN_WS_[workspace ID]]`.
-This is conveniently set by `ascli` using an empty string for field `with`.
+In order to declare/create the shared folder in the workspace, a special value for `access_id` is used: `ASPERA_ACCESS_KEY_ADMIN_WS_[workspace ID]`, with a `access_type` of `user`.
+This is conveniently set by `ascli` using an **empty string** for field `with`.
 In order to share a folder with a different, special tags are set, but this is conveniently done by `ascli` using the `as` field.
 
 ##### User Shared Folders
@@ -5891,11 +6129,11 @@ ascli aoc files permission --workspace=<workspace name> <path to folder> ...
 
 > [!NOTE]
 > The workspace is identified by name, and folder by path, relative to the user's home.
-> To use an identifier instead, one can use the percent selector, like `%id:1234`
+> To use an identifier instead, one can use the percent selector, like `%id:_my_ws_id_`.
 
 ##### Admin Shared Folders
 
-Admin shared folders, created by administrators in a workspace follow the syntax:
+Admin shared folders, created by administrators in a workspace, follow the syntax:
 
 ```shell
 ascli aoc admin node do <node ID> permission --workspace=<workspace name> <path to folder>
@@ -5903,9 +6141,11 @@ ascli aoc admin node do <node ID> permission --workspace=<workspace name> <path
 
 > [!TIP]
 > The node is identified by identifier.
-> To use an name instead, one can use the percent selector, like `%name:"my node"`
+> To use an name instead, one can use the percent selector, like `%name:"my node"`.
+> The path is identifier by a path, one can specify a file id, with `%id:123`.
+> If the id is left blank: `%id:`, then if means `*`, i.e. all.
 
-##### Example: List permissions on a shared folder
+##### Example: List permissions on a user shared folder
 
 ```shell
 ascli aoc files permission /shared_folder_test1 list
@@ -5952,7 +6192,7 @@ To remove a password:
 > [!NOTE]
 > Access level cannot be customized in this version.
 
-An expiration date can be set with parameter `expires_at`, using ISO 8601 format.
+An expiration date can be set with parameter `expires_at`, using [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
 E.g. `2025-08-29T08:10:31.000Z`.
 If only a date is provided, it will be set to midnight UTC of that date.
 
@@ -5960,16 +6200,16 @@ If only a date is provided, it will be set to midnight UTC of that date.
 
 First, identify the node ID where the shared folder will be created.
 
-To get the node ID of the default node for workspace `my ws`, use the command:
+To get the node ID of the default node for workspace `<workspace_name>`, use the command:
 
 ```shell
-ascli aoc admin workspace show %name:'my ws' --fields=node_id
+ascli aoc admin workspace show %name:'<workspace_name>' --fields=node_id
 ```
 
 Alternatively (longer):
 
 ```shell
-ascli aoc admin workspace list --select=@json:'{"name":"my ws"}' --fields=node_id
+ascli aoc admin workspace list --select=@json:'{"name":"<workspace_name>"}' --fields=node_id
 ```
 
 Or select a node identifier manually from the list of nodes:
@@ -5980,24 +6220,22 @@ ascli aoc admin node list --fields=id,name
 
 In the following commands, replace:
 
-- `1234` with the node ID
-- `my ws` with the workspace name
-- `/folder_on_node` with the name of the folder on the node: it can also be a folder deeper than level 1.
-
-The node can also be conveniently identified using the **percent selector** instead of numerical ID: `%name:"my node"`.
+- `<node_id>` with the node ID, or with `%name:<node_name>`.
+- `<workspace_name>` with the workspace name, or with `%id:<workspace_id>`.
+- `<folder_path>` with the path of the folder to share on the node (e.g. `/my_folder` or simply `my_folder`). It can also be a folder deeper than level 1.
 
 If the shared folder does not exist, then create it:
 
 ```shell
-ascli aoc admin node do 1234 mkdir /folder_on_node
+ascli aoc admin node do <node_id> mkdir <folder_path>
 ```
 
-Create the shared folder in workspace `my ws` (set `with` to empty string, or do not specify it).
-Optionally use `as` to set the name of the shared folder if different from the folder name on the node.
+Create the shared folder in workspace `<workspace_name>` (set `with` to empty string, or do not specify it).
+**Optionally**, use `as` to set the name of the shared folder if different from the folder name on the node.
 For other options, refer to the previous section on shared folders.
 
 ```shell
-ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"","as":"folder_for_users"}' --workspace="my ws"
+ascli aoc admin node do <node_id> permission <folder_path> create @json:'{"with":"","as":"folder_for_users"}' --workspace="<workspace_name>"
 ```
 
 > [!NOTE]
@@ -6008,20 +6246,81 @@ The `"with"` parameter will perform a lookup, and set fields `access_type` and `
 The native fields `access_type` and `access_id` can also be used, instead of `with`.
 
 ```shell
-ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"john@example.com","as":"folder_for_one_user"}' --workspace="my ws"
+ascli aoc admin node do <node_id> permission <folder_path> create @json:'{"with":"john@example.com","as":"folder_for_one_user"}' --workspace="<workspace_name>"
 ```
 
 ```shell
-ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"group 1","as":"folder_for_a_group"}' --workspace="my ws"
+ascli aoc admin node do <node_id> permission <folder_path> create @json:'{"with":"group 1","as":"folder_for_a_group"}' --workspace="<workspace_name>"
 ```
 
 ```shell
-ascli aoc admin node do 1234 permission /folder_on_node create @json:'{"with":"my ws","as":"folder_for_all_workspace"}' --workspace="my ws"
+ascli aoc admin node do <node_id> permission <folder_path> create @json:'{"with":"<workspace_name>","as":"folder_for_all_workspace"}' --workspace="<workspace_name>"
 ```
 
 > [!NOTE]
 > In the previous commands, field `as` is optional.
 
+##### Example: List all workspace admin shared folder in a workspace
+
+```shell
+ascli aoc admin workspace shared_folder %name:'<workspace_name>' list
+```
+
+```text
+╭───────┬───────────┬─────────┬─────────┬───────────┬──────────────────────────────────────╮
+│ id    │ node_name │ node_id │ file_id │ file.path │ tags.aspera.files.workspace.share_as │
+╞═══════╪═══════════╪═════════╪═════════╪═══════════╪══════════════════════════════════════╡
+│ 198   │ eudemo    │ 8666    │ 2465    │ /project1 │                                      │
+│ 785   │ eudemo    │ 8666    │ 9       │ /folder2  │ project2                             │
+│ 4788  │ eudemo    │ 8666    │ 3691    │ /backup   │                                      │
+╰───────┴───────────┴─────────┴─────────┴───────────┴──────────────────────────────────────╯
+```
+
+To list members:
+
+```shell
+ascli aoc admin workspace shared_folder %name:'<workspace_name>' member 198 list
+```
+
+```text
+╭─────────────┬──────────────────────────────────┬──────────────┬──────────────────────╮
+│ access_type │ access_id                        │ access_level │ last_updated_at      │
+╞═════════════╪══════════════════════════════════╪══════════════╪══════════════════════╡
+│ user        │ ASPERA_ACCESS_KEY_ADMIN_WS_45071 │ edit         │ 2020-11-29T22:48:49Z │
+│ group       │ 160270                           │ edit         │ 2024-05-13T15:58:02Z │
+╰─────────────┴──────────────────────────────────┴──────────────┴──────────────────────╯
+```
+
+If you have the node id of the shared folder, than it is equivalent to:
+
+```shell
+ascli aoc admin node do 8669 perm /project1 list --query=@json:'{"tag":"aspera.files.workspace.id=<workspace_id>"}'
+```
+
+##### Example: List all workspace admin shared folder on a node
+
+First get the workspace identifier:
+
+```shell
+ascli aoc admin workspace list --select=@json:'{"name":"<workspace_name>"}' --fields=id
+```
+
+```text
+<workspace_id>
+```
+
+Then, identify the node id on which to list, see previous section.
+
+Finally, list all shared folders, as permissions:
+
+```shell
+ascli aoc admin node do <node_id> perm %id: list --query=@json:'{"access_type":"user","access_id":"ASPERA_ACCESS_KEY_ADMIN_WS_<workspace_id>"}'
+```
+
+> [!NOTE]
+> Refer to Node API: `GET /permissions` for all `query` options.
+> The folder identifier is left empty `%id:`, to apply to all folders.
+
 #### Cross Organization transfers
 
 It is possible to transfer files directly between organizations without having to first download locally and then upload...
@@ -6030,7 +6329,7 @@ Although optional, the creation of [Option Preset](#option-preset) is recommende
 
 Procedure to send a file from org1 to org2:
 
-- Get access to Organization 1 and create an [Option Preset](#option-preset): e.g. `org1`, for instance, use the [Wizard](#configuration-using-wizard)
+- Get access to Organization 1 and create an [Option Preset](#option-preset): e.g. `org1`, for instance, use the [Wizard](#wizard)
 - Check that access works and locate the source file e.g. `mysourcefile`, e.g. using command `files browse`
 - Get access to Organization 2 and create an [Option Preset](#option-preset): e.g. `org2`
 - Check that access works and locate the destination folder `mydestfolder`
@@ -6072,12 +6371,12 @@ For instructions, refer to section `find` for plugin `node`.
 > Add `ascli aoc` in front of the following commands:
 
 ```bash
-admin analytics transfers nodes
+admin analytics files organization '' aoc_transfer_id
 admin analytics transfers organization --query=@json:'{"status":"completed","direction":"receive","limit":2}' --notify-to=my_email_external --notify-template=@ruby:'%Q{From: <%=from_name%> <<%=from_email%>>\nTo: <<%=to%>>\nSubject: <%=ev["files_completed"]%> files received\n\n<%=ev.to_yaml%>}'
 admin analytics transfers users --once-only=yes
 admin application list
-admin ats access_key create --cloud=aws --region=my_region --params=@json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
-admin ats access_key create --cloud=softlayer --region=my_region --params=@json:'{"id":"ak1ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
+admin ats access_key create --cloud=aws --region=my_region @json:'{"id":"ak_aws_aoc","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
+admin ats access_key create --cloud=softlayer --region=my_region @json:'{"id":"ak1ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
 admin ats access_key delete ak1ibmcloud
 admin ats access_key list --fields=name,id
 admin ats access_key node ak1ibmcloud --secret=my_secret_here browse /
@@ -6122,15 +6421,18 @@ admin subscription usage
 admin subscription usage MONTH
 admin user list
 admin user modify %name:my_user_email @json:'{"deactivated":false}'
+admin workspace dropbox %name:my_other_workspace list
 admin workspace list
+admin workspace shared_folder %name:my_other_workspace list
+admin workspace shared_folder %name:my_other_workspace member shared_folder_id list
 admin workspace_membership list
 admin workspace_membership list --fields=ALL --query=@json:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
-automation workflow action wf_id create @json:'{"name":"toto"}' \
+automation workflow action wf_id create @json:'{"name":"toto"}'
 automation workflow create @json:'{"name":"test_workflow"}'
 automation workflow delete wf_id
 automation workflow list
 automation workflow list --query=@json:'{"show_org_workflows":"true"}' --scope=admin:all
-automation workflow list --select=@json:'{"name":"test_workflow"}' --fields=id --format=csv --display=data --output=test
+automation workflow list --select=@json:'{"name":"test_workflow"}' --fields=id
 bearer_token --display=data --scope=user:all
 files bearer /
 files bearer_token_node / --cache-tokens=no
@@ -6143,7 +6445,7 @@ files browse my_remote_folder
 files browse my_remote_folder/
 files cat testdst/test_file.bin
 files delete /testsrc
-files down --to-folder=. testdst/test_file.bin testdst/test_file.bin
+files download --to-folder=. testdst/test_file.bin testdst/test_file.bin
 files download --transfer=connect testdst/test_file.bin
 files download --transfer=desktop testdst/test_file.bin
 files find /
@@ -6151,7 +6453,6 @@ files find / '\.partial$'
 files find / @ruby:'->(f){f["type"].eql?("file")}'
 files mkdir /testsrc
 files modify /some_folder @json:'{"mount_point":false}'
-files modify my_test_folder
 files permission my_test_folder list
 files rename /some_folder testdst
 files short_link /testdst private create
@@ -6168,9 +6469,8 @@ files transfer push /testsrc --to-folder=/testdst test_file.bin
 files upload --to-folder=/ test_file.bin --url=my_public_link_folder_no_pass
 files upload --to-folder=/testsrc test_file.bin
 files upload --to-folder=/testsrc test_file.bin test_file.bin
-files upload --workspace=my_other_workspace --to-folder=my_other_folder test_file.bin --transfer=node --transfer-info=@json:@stdin:
 files v3 info
-gateway --pid-file=pid_aocfxgw @json:'{"url":"https://localhost:12345/aspera/faspex"}' &
+gateway @json:'{"url":"https://localhost:12345/aspera/faspex"}'
 organization
 organization --format=image --fields=background_image_url --ui=text
 organization --url=my_public_link_recv_from_aoc_user
@@ -6182,14 +6482,13 @@ packages receive ALL --once-only=yes --to-folder=. --lock-port=12345 --query=@js
 packages receive INIT --once-only=yes --query=@json:'{"dropbox_name":"my_shared_inbox_name"}'
 packages receive package_id3 --to-folder=.
 packages receive package_id3 --to-folder=. / --package-folder=name
-packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' test_file.bin
-packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":{"Project Id":"456","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
-packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_meta"],"metadata":{"Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
-packages send --workspace=my_workspace_shared_inbox @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_shared_inbox_name"]}' test_file.bin
-packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_external"]}' --new-user-option=@json:'{"package_contact":true}' test_file.bin
-packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal"],"note":"my note"}' test_file.bin
-packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin --url=my_public_link_send_aoc_user --password=my_public_link_send_use_pass
-packages send @json:'{"name":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin --url=my_public_link_send_shared_inbox
+packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"package title","recipients":["my_shared_inbox_meta"],"metadata":[{"input_type":"single-text","name":"Project Id","values":["123"]},{"input_type":"single-dropdown","name":"Type","values":["Opt2"]},{"input_type":"multiple-checkbox","name":"CheckThose","values":["Check1","Check2"]},{"input_type":"date","name":"Optional Date","values":["2021-01-13T15:02:00.000Z"]}]}' test_file.bin
+packages send --workspace=my_workspace_shared_inbox --validate-metadata=yes @json:'{"name":"package title","recipients":["my_shared_inbox_meta"],"metadata":{"Project Id":"456","Type":"Opt2","CheckThose":["Check1","Check2"],"Optional Date":"2021-01-13T15:02:00.000Z"}}' test_file.bin
+packages send --workspace=my_workspace_shared_inbox @json:'{"name":"package title","recipients":["my_shared_inbox_name"]}' test_file.bin
+packages send @json:'{"name":"package title","recipients":["my_email_external"]}' --new-user-option=@json:'{"package_contact":true}' test_file.bin
+packages send @json:'{"name":"package title","recipients":["my_email_internal"],"note":"my - note"}' test_file.bin
+packages send @json:'{"name":"package title"}' test_file.bin --url=my_public_link_send_aoc_user --password=my_public_link_send_use_pass
+packages send @json:'{"name":"package title"}' test_file.bin --url=my_public_link_send_shared_inbox
 packages shared_inboxes list
 packages shared_inboxes show %name:my_shared_inbox_name
 remind --username=my_user_email
@@ -6336,10 +6635,9 @@ The parameters provided to ATS for access key creation are the ones of [ATS API]
 
 ```bash
 access_key cluster ak2ibmcloud --secret=my_secret_here
-access_key create --cloud=aws --region=my_region --params=@json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
-access_key create --cloud=softlayer --region=my_region --params=@json:'{"id":"ak2ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
+access_key create --cloud=aws --region=my_region @json:'{"id":"ak_aws","name":"my test key AWS","storage":{"type":"aws_s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
+access_key create --cloud=softlayer --region=my_region @json:'{"id":"ak2ibmcloud","secret":"my_secret_here","name":"my test key","storage":{"type":"ibm-s3","bucket":"my_bucket","credentials":{"access_key_id":"my_access_key","secret_access_key":"my_secret_key"},"path":"/"}}'
 access_key delete ak2ibmcloud
-access_key delete ak_aws
 access_key entitlement ak2ibmcloud
 access_key list --fields=name,id
 access_key node ak2ibmcloud browse / --secret=my_secret_here
@@ -6379,7 +6677,7 @@ ascli server --url=ssh://hsts.example.com:33001 --username=john --ssh-keys=~/.ss
 
 ```bash
 browse /
-browse / --password=@none: --ssh-options=@json:'{"number_of_password_prompts":0}' --ssh-keys=$aspera_key_path
+browse / --password=@none: --ssh-options=@json:'{"number_of_password_prompts":0}' --ssh-keys=serv_key_path
 browse my_inside_folder/test_file.bin
 browse my_upload_folder/target_hot
 cp my_inside_folder/test_file.bin my_upload_folder/200KB.2
@@ -6389,24 +6687,26 @@ df
 download my_inside_folder/test_file.bin --to-folder=. --transfer-info=@json:'{"wss":false,"resume":{"iter_max":1}}'
 download my_large_file --to-folder=my_upload_folder --transfer=node --ts.resume_policy=none
 du /
+health transfer --to-folder=my_upload_folder
 health transfer --to-folder=my_upload_folder --format=nagios
 info
 md5sum my_inside_folder/test_file.bin
 mkdir my_inside_folder --logger=stdout
 mkdir my_upload_folder/target_hot
 mv my_upload_folder/200KB.2 my_upload_folder/to.delete
+sync admin file_info /data/local_sync
+sync admin overview /data/local_sync
 sync admin status /data/local_sync
+sync pull my_inside_folder --to-folder=/data/local_sync @json:'{"name":"serv_sync_pull_conf","reset":true,"transport":{"target_rate":my_bps}}'
 sync pull my_inside_folder --to-folder=/data/local_sync @json:'{"name":"serv_sync_pull_conf"}'
-upload 'faux:///test1?100m' 'faux:///test2?100m' --to-folder=/Upload --ts=@json:'{"target_rate_kbps":1000000,"resume_policy":"none","precalculate_job_size":true}'
-upload 'faux:///test1?100m' 'faux:///test2?100m' --to-folder=/Upload --ts=@json:'{"target_rate_kbps":1000000,"resume_policy":"none","precalculate_job_size":true}' --transfer-info=@json:'{"quiet":false}' --progress=no
-upload 'test_file.bin' --to-folder=my_inside_folder --ts=@json:'{"multi_session":3,"multi_session_threshold":1,"resume_policy":"none","target_rate_kbps":100000}' --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}' --progress-bar=yes
 upload --sources=@ts --transfer-info=@json:'{"ascp_args":["--file-list","filelist.txt"]}' --to-folder=my_inside_folder
 upload --sources=@ts --transfer-info=@json:'{"ascp_args":["--file-pair-list","file_pair_list.txt"]}'
 upload --sources=@ts --ts=@json:'{"paths":[{"source":"test_file.bin","destination":"my_inside_folder/other_name_4"}]}' --transfer=transferd
-upload --src-type=pair 'test_file.bin' my_inside_folder/other_name_2 --notify-to=my_email_external --transfer-info=@json:'{"ascp_args":["-l","100m"]}'
 upload --src-type=pair --sources=@json:'["test_file.bin","my_inside_folder/other_name_3"]' --transfer-info.quiet=false --progress=no
+upload --src-type=pair test_file.bin my_inside_folder/other_name_2 --notify-to=my_email_external --transfer-info=@json:'{"ascp_args":["-l","100m"]}'
 upload --src-type=pair test_file.bin my_upload_folder/other_name_5 --ts=@json:'{"cipher":"aes-192-gcm","content_protection":"encrypt","content_protection_password":"my_secret_here","cookie":"biscuit","create_dir":true,"delete_before_transfer":false,"delete_source":false,"exclude_newer_than":"-1","exclude_older_than":"-10000","fasp_port":33001,"http_fallback":false,"multi_session":0,"overwrite":"diff+older","precalculate_job_size":true,"preserve_access_time":true,"preserve_creation_time":true,"rate_policy":"fair","resume_policy":"sparse_csum","symlink_policy":"follow"}'
 upload --to-folder=my_upload_folder/target_hot --lock-port=12345 --transfer-info=@json:'{"ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}' source_hot
+upload test_file.bin --to-folder=my_inside_folder --ts=@json:'{"multi_session":3,"multi_session_threshold":1,"resume_policy":"none","target_rate_kbps":100000}' --transfer-info=@json:'{"spawn_delay_sec":2.5,"multi_incr_udp":false}' --progress-bar=yes
 ```
 
 ### Authentication on Server with SSH session
@@ -6548,11 +6848,11 @@ Native API parameters can be placed in option `query`.
 
 Special parameters can be placed in option `query` for "gen3" browse:
 
-| Parameter   | Description |
-|-------------|-------------|
-| `recursive` | Recursively list files |
-| `max`       | Maximum number of files to list |
-| `self`      | Offset in the list |
+| Parameter   | Description                      |
+|-------------|----------------------------------|
+| `recursive` | Recursively list files.          |
+| `max`       | Maximum number of files to list. |
+| `self`      | Offset in the list.              |
 
 Option `node_cache` can be set to `no` to avoid use of folder cache (Redis) and force actual read of file system.
 
@@ -6670,13 +6970,13 @@ By providing the `validator` option, offline transfer validation can be done.
 
 ### Sync
 
-There are three commands related to file synchronisation:
+There are three commands related to file synchronization in `node`:
 
 | Command | `node` | `shares` | `aoc` | `server` | Description |
-|---------|--------|----------|-------|----------|-------------|
-| `sync`  | Yes    | Yes      | Yes   | Yes      | Perform a local sync, by executing `async` locally. |
-| `async` | Yes    |          |       |          | Uses API `/async`.<br/>Get status on sync operation on server side, like Aspera Console. |
-| `ssync` | Yes    |          |       |          | Uses API `/asyncs`.<br/>It can start a sync operation on the server side, and monitor only those. |
+|-----|-----|-----|-----|-----|-----------------------------------------------|
+| `sync`  | Yes | Yes | Yes | Yes | Perform a local sync, by executing `async` locally. |
+| `async` | Yes |     |     |     | Uses API `/async`.<br/>Get status on sync operation on server side, like Aspera Console. |
+| `ssync` | Yes |     |     |     | Uses API `/asyncs`.<br/>It can start a sync operation on the server side, and monitor only those. |
 
 For details on the `sync` action, refer to [IBM Aspera Sync](#ibm-aspera-sync).
 
@@ -6821,17 +7121,17 @@ Bearer tokens can be generated using `ascli` command `bearer_token`: it takes tw
 - The private key used to sign the token.
 - The token information, which is a `Hash` containing the following elements:
 
-| Parameter          | Default           | Type      | Description                      |
-|--------------------|-------------------|-----------|----------------------------------|
-| `_scope`           | `user:all`        | Special   | Either `user:all` or `admin:all` |
-| `_validity`        | 86400             | Special   | Validity in seconds from now.    |
-| `user_id`          | -                 | Mandatory | Identifier of user               |
-| `scope` | `node.<access_key>:<_scope>` | Mandatory | API scope, e.g. `node.<access_key>:<node scope>`         |
-| `expires_at`       | `now+<_validity>` | Mandatory | Format: `%Y-%m-%dT%H:%M:%SZ` e.g. `2021-12-31T23:59:59Z` |
-| `auth_type`        | `access_key`      | Optional  | `access_key`, `node_user`        |
-| `group_ids`        | -                 | Optional  | List of group IDs                |
-| `organization_id`  | -                 | Optional  | Organization ID                  |
-| `watermarking_json_base64` | -         | Optional  | Watermarking information (not used) |
+| Parameter              | Default                 | Type    | Description                           |
+|----------------------|---------------------------|---------|---------------------------------------|
+| `_scope`               | `user:all`              | Special | Either `user:all` or `admin:all`      |
+| `_validity`            | 86400                   | Special | Validity in seconds from now.         |
+| `user_id`              | -                     | Mandatory | Identifier of user                    |
+| `scope`     | `node.<access_key>:<_scope>`     | Mandatory | API scope<br/>e.g. `node.<access_key>:<node scope>`         |
+| `expires_at`           | `now+<_validity>`     | Mandatory | Format: `%Y-%m-%dT%H:%M:%SZ`<br/>e.g. `2021-12-31T23:59:59Z` |
+| `auth_type`            | `access_key`          | Optional  | `access_key`, `node_user`             |
+| `group_ids`            | -                     | Optional  | List of group IDs                     |
+| `organization_id`      | -                     | Optional  | Organization ID                       |
+| `watermarking_json_base64` | -                 | Optional  | Watermarking information (not used)   |
 
 > [!NOTE]
 > For convenience, `ascli` provides additional parameters `_scope` and `_validity`.
@@ -6950,7 +7250,7 @@ ascli node -N --url=https://... --password="Bearer $(cat bearer.txt)" --root-id=
 > Add `ascli node` in front of the following commands:
 
 ```bash
---url=https://tst.example.com/path --password="Bearer bearer_666" --root-id=root_id access_key do self br /
+--url=https://tst.example.com/path --password='Bearer node_bearer_token' --root-id=bearer_root_id access_key do self browse /
 access_key create @json:'{"id":"my_username","secret":"my_password_here","storage":{"type":"local","path":"/"}}'
 access_key delete my_username
 access_key do my_ak_name browse /
@@ -6961,31 +7261,29 @@ access_key do my_ak_name find my_test_folder
 access_key do my_ak_name find my_test_folder @re:'\.jpg$'
 access_key do my_ak_name find my_test_folder @ruby:'->(f){f["name"].end_with?(".jpg")}'
 access_key do my_ak_name mkdir /tst_nd_ak
-access_key do my_ak_name mkfile /mkfile.txt "hello world"
+access_key do my_ak_name mkfile /mkfile.txt 'hello world'
 access_key do my_ak_name mklink /mklink.txt --query=@json:'{"target":"/mkfile.txt","target_node_id":"123"}'
 access_key do my_ak_name node_info /
 access_key do my_ak_name rename /tst_nd_ak test_nd_ak2
 access_key do my_ak_name show %id:1
-access_key do my_ak_name show /test_nd_ak3
 access_key do my_ak_name upload 'faux:///test_nd_ak3?100k' --default-ports=no
-access_key do self permission %id:root_id create @json:'{"access_type":"user","access_id":"666"}'
+access_key do self permission %id:bearer_root_id create @json:'{"access_type":"user","access_id":"666"}'
+access_key do self permission / delete 1
 access_key do self permission / show 1
-access_key do self show / --fields=id --output=root_id
 access_key list
 access_key set_bearer_key self @file:my_private_key
 access_key show %id:self
 api_details
 asperabrowser
-async bandwidth %name:SYNC_NAME
-async counters %name:SYNC_NAME
+async bandwidth %name:my_sync_session_name
+async counters %name:my_sync_session_name
 async delete ALL
-async files %name:SYNC_NAME
-async files %name:SYNC_NAME --once-only=yes
+async files %name:my_sync_session_name
+async files %name:my_sync_session_name --once-only=yes
 async list
-async show %name:SYNC_NAME
+async show %name:my_sync_session_name
 async show ALL
 basic_token
-bearer_token @file:my_private_key @json:'{"user_id":"666"}' --output=bearer_666
 browse / --log-level=trace2
 cat my_upload_folder/test_file.bin
 central file list
@@ -6998,7 +7296,7 @@ health
 info --fpac='function FindProxyForURL(url,host){return "DIRECT"}'
 license
 mkdir my_upload_folder/a_folder
-mkfile my_upload_folder/a_file1 "hello world"
+mkfile my_upload_folder/a_file1 'hello world'
 mklink my_upload_folder/a_folder my_upload_folder/tdlink
 rename my_upload_folder a_file1 a_file
 search / --query=@json:'{"sort":"mtime"}'
@@ -7007,6 +7305,7 @@ service delete service1
 service list
 slash
 space /
+spec
 ssync bandwidth %name:my_node_sync
 ssync counters %name:my_node_sync
 ssync create @json:'{"configuration":{"name":"my_node_sync","local":{"path":"my_local_path_real"},"remote":{"host":"my_host","port":my_port,"user":"my_username","pass":"my_password_here","path":"my_remote_path"}}}'
@@ -7020,16 +7319,20 @@ ssync stop %name:my_node_sync
 ssync summary %name:my_node_sync
 stream list
 sync admin status /data/local_sync
-sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"name":"SYNC_NAME","reset":true}'
+sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"name":"my_sync_session_name","reset":true}'
 sync pull /aspera-test-dir-tiny --to-folder=/data/local_sync @json:'{"reset":true}'
-transfer list --once-only=yes
+transfer bandwidth_average
+transfer cancel nd_xfer_id
 transfer list --query=@json:'{"active_only":true}'
 transfer list --query=@json:'{"reset":true}' --once-only=yes
+transfer modify nd_xfer_id @json:'{"target_rate_kbps":10000}'
 transfer sessions
+transfer show nd_xfer_id
 transport
+upload 'faux:///testfile1?1m' --to-folder=my_local_path
 upload --to-folder=my_upload_folder --sources=@ts --ts=@json:'{"paths":[{"source":"/aspera-test-dir-small/10MB.2"}],"precalculate_job_size":true}' --transfer=node --transfer-info=@json:'{"url":"https://node.example.com/path@","username":"my_username","password":"my_password_here"}'
 upload --username=my_ak_name --password=my_ak_secret test_file.bin
-upload test_file.bin --to-folder=my_upload_folder --ts=@json:'{"target_rate_cap_kbps":10000}'
+upload my_mxf my_docx --ts=@json:'{"target_rate_kbps":1000000,"resume_policy":"none"}'
 watch_folder list
 ```
 
@@ -7044,10 +7347,10 @@ The `node` plugin supports Open Telemetry (OTel) for monitoring and tracing.
 
 The command expects the following parameters provided as a `Hash` positional parameter:
 
-| Parameter   | Type     | Default | Description                                      |
-|-------------|----------|---------|---------------------------------------------------|
-| `url`       | `String` | -       | URL of the Instana HTTPS backend for OTel.        |
-| `key`       | `String` | -       | Agent key for the backend.                        |
+| Parameter   | Type     | Default | Description                                  |
+|-------------|----------|---------|----------------------------------------------|
+| `url`       | `String` | -       | URL of the Instana HTTPS backend for OTel.   |
+| `key`       | `String` | -       | Agent key for the backend.                   |
 | `interval`  | `Float`  | 10      | Polling interval in seconds.<br/>`0` for single shot. |
 
 To retrieve OTel backend information: Go to the Instana web interface, **More** &rarr; **Agents** &rarr; **Docker** and identify the agent endpoint and key, e.g. `endpoint=ingress-blue-saas.instana.io`.
@@ -7085,7 +7388,9 @@ IBM Aspera's newer self-managed application.
 | `boot`        | Use authentication token copied from browser (experimental)         |
 
 > [!TIP]
-> If you have a Faspex 5 public link, provide it, unchanged, through the option `url`
+> If you have a Faspex 5 public link, provide it, as-is, through the option `url`.
+
+### Faspex 5 quick start with wizard
 
 For a quick start, one can use the wizard, which will help to create an [Option Preset](#option-preset):
 
@@ -7093,8 +7398,15 @@ For a quick start, one can use the wizard, which will help to create an [Option
 ascli config wizard
 ```
 
+Then, answer questions interactively:
+
 ```text
 argument: url> faspex5.example.com
+```
+
+Potentially, multiple applications may be detected, or if only Faspex is detected, it would skip this step:
+
+```text
 Multiple applications detected:
 +---------+-------------------------------------------+-------------+
 | product | url                                       | version     |
@@ -7103,12 +7415,28 @@ Multiple applications detected:
 | server  | ssh://faspex5.example.com:22              | OpenSSH_8.3 |
 +---------+-------------------------------------------+-------------+
 product> faspex5
+```
+
+When Faspex is detected, it would ask for the path to a private key.
+If you don't have a private key, then leave that field blank, and it will generate one or use one that was previously generated.
+
+```test
 Using: Faspex at https://faspex5.example.com/aspera/faspex
 Please provide the path to your private RSA key, or nothing to generate one:
 option: key_path>
 Using existing key:
 /Users/someuser/.aspera/ascli/my_key
+```
+
+Then, the email of the user shall be provided:
+
+```text
 option: username> someuser@example.com
+```
+
+The administrator of Faspex shall provide you with a `client_id`, as specified below.
+
+```text
 Ask the ascli client ID and secret to your Administrator.
 Admin should login to: https://faspex5.example.com/aspera/faspex
 Navigate to: ::  → Admin → Configurations → API clients
@@ -7132,10 +7460,16 @@ Saving configuration file.
 ```
 
 > [!NOTE]
-> Paste the entire public key, including the BEGIN and END lines, into the user profile.
+> Paste the entire public key, including the BEGIN and END lines, into the user's profile.
 
 For more information on the JWT method, refer to the section below.
 
+If you have generated a private key with the wizard and lost the public key, you can retrieve the public key like this:
+
+```shell
+ascli faspex5 --show-config --show-secrets=yes --fields=private_key | ascli conf pubkey @stdin: --show-secrets=yes
+```
+
 ### Faspex 5 JWT authentication
 
 This is the general purpose and **recommended** method to use.
@@ -7156,15 +7490,15 @@ Activation is in two steps:
 
 - The user will authenticate with a private key and set the public key in his Faspex 5 profile.
 
-  > [!TIP]
-  > If you don’t have a private key, see [Private Key](#private-key) to generate one.
-  
   This operation is done by each user using the CLI.
 
   - As a user, click the user logo located to the left of the app switcher in the top-right corner.
   - Select `Account Settings`.
   - At the bottom, in the `Public key in PEM format` field, paste the **public key** that corresponds to the private key assigned to your account.
 
+> [!TIP]
+> If you don’t have a private key, see [Private Key](#private-key) to generate one.
+
 Then use these options:
 
 ```text
@@ -7210,6 +7544,16 @@ The user will use the following options:
 --redirect-uri=https://127.0.0.1:8888
 ```
 
+### Faspex 5 public link authentication
+
+If all you have is a public link received by email or other, you can still do authorized actins with it.
+
+For example, for a public link to post a package:
+
+```shell
+ascli faspex5 packages send --url='https://faspex5.example.com/?context=_some_long_string_here_'
+```
+
 ### Faspex 5 bootstrap authentication
 
 For `boot` method: (will be removed in future)
@@ -7242,8 +7586,8 @@ admin distribution_lists delete %name:test4
 admin distribution_lists list --query=@json:'{"type":"global"}'
 admin email_notifications list
 admin email_notifications show welcome_email
-admin event app --query=@json:'{"max":20}'
-admin event web
+admin event application --query=@ruby:'{"event_type[]"=>["login_success"],"created_at_start"=>(Time.now.utc-60).strftime("%Y-%m-%dT%H:%M:%S.%LZ")}'
+admin event webhook
 admin jobs list --query=@json:'{"job_type":"email","status":"failed"}' --fields=id,error_desc
 admin metadata_profiles list
 admin node browse %name:Local
@@ -7258,7 +7602,7 @@ admin saml_configs list
 admin shared_inboxes invite %name:my_shared_box_name johnny@example.com
 admin shared_inboxes list
 admin shared_inboxes list --query=@json:'{"all":true}'
-admin shared_inboxes members %name:my_shared_box_name create %name:john@example.com
+admin shared_inboxes members %name:my_shared_box_name create %name:john@example.com submit_only
 admin shared_inboxes members %name:my_shared_box_name delete %name:john@example.com
 admin shared_inboxes members %name:my_shared_box_name delete %name:johnny@example.com
 admin shared_inboxes members %name:my_shared_box_name list
@@ -7268,38 +7612,40 @@ admin smtp show
 admin smtp test my_email_external
 admin workgroups list
 bearer_token
-gateway --pid-file=pid_f5_fxgw @json:'{"url":"https://localhost:12346/aspera/faspex"}' &
-health
+gateway @json:'{"url":"https://localhost:12346/aspera/faspex"}'
+health --url=https://faspex5.example.com/path
 invitation list
 invitations create @json:'{"email_address":"aspera.user1+u@gmail.com"}'
-packages browse f5_pack_id --query=@json:'{"recursive":true}'
-packages delete f5_pack_id
+packages browse f5_package_id --query=@json:'{"recursive":true}'
+packages delete f5_package_id
 packages list --box=ALL
 packages list --box=my_shared_box_name
 packages list --box=my_workgroup --group-type=workgroups
 packages list --box=outbox --fields=DEF,sender.email,recipients.0.recipient_type
 packages list --query=@json:'{"mailbox":"inbox","status":"completed"}'
-packages receive --box=my_shared_box_name package_box_id1 --to-folder=.
+packages receive --box=my_shared_box_name f5_pack_shboxc --to-folder=.
 packages receive --box=my_workgroup --group-type=workgroups workgroup_package_id1 --to-folder=.
 packages receive ALL --once-only=yes --to-folder=.
 packages receive INIT --once-only=yes
-packages receive f5_pack_id --to-folder=. --ts=@json:'{"content_protection_password":"my_secret_here"}'
-packages send --shared-folder=%name:my_shared_folder_name @json:'{"title":"test title","recipients":["my_email_internal"]}' my_shared_folder_file --fields=id --display=data --output=f5_pack_id
+packages receive f5_package_id --to-folder=. --ts=@json:'{"content_protection_password":"my_secret_here"}'
 packages send --url=my_public_link_send_f5_user @json:'{"title":"test title"}' test_file.bin
 packages send --url=my_public_link_send_shared_box @json:'{"title":"test title"}' test_file.bin
 packages send @json:'{"title":"test title","recipients":["my_shared_box_name"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' test_file.bin
 packages send @json:'{"title":"test title","recipients":["my_workgroup"]}' test_file.bin
 packages send @json:'{"title":"test title","recipients":[{"name":"my_username"}]my_meta}' test_file.bin --ts=@json:'{"content_protection_password":"my_secret_here"}'
-packages show --box=my_shared_box_name package_box_id1
+packages send @json:'{"title":"test_webhook_ascli","recipients":["my_shared_box_name"]}' 'faux:///test1?1m'
+packages show --box=my_shared_box_name f5_pack_shboxc
 packages show --box=my_workgroup --group-type=workgroups workgroup_package_id1
-packages show f5_pack_id
-packages status f5_pack_id
-postprocessing --pid-file=pid_f5_postproc @json:'{"url":"https://localhost:8553/asclihook","script_folder":"","cert":"localhost.p12","key":"changeit"}' &
+packages show f5_package_id
+packages status f5_p3a @list:,failed,completed
+packages status f5_package_id
+postprocessing @json:'{"url":"https://localhost:8553/asclihook","script_folder":"$(TST)","cert":"$(TMP / "localhost.p12")","key":"changeit"}'
 shared browse %name:my_src
 shared list
 shared_folders browse %name:my_shared_folder_name
 shared_folders list
 user account
+user account --query.expand=true
 user profile modify @json:'{"preference":{"connect_disabled":false}}'
 user profile show
 version
@@ -7319,7 +7665,7 @@ By default, package operations (`send`, `receive`, `list`) are performed on the
 To select another inbox, use option `box` with one of the following values:
 
 | `box`               | Comment |
-|---------------------|---------|
+|---------------------|----------------------------------------------------------------------|
 | `inbox`             | Default |
 | `inbox_history`     | |
 | `inbox_all`         | |
@@ -7329,8 +7675,8 @@ To select another inbox, use option `box` with one of the following values:
 | `pending`           | |
 | `pending_history`   | |
 | `all`               | |
-| `ALL`               | **admin only**, all inboxes of all users |
-| Open value          | Name of a shared inbox if `group_type` is `shared_inboxes` (default)<br/>or workgroup if `group_type` is `workgroups` |
+| `ALL`               | All inboxes of all users. **admin only**. |
+| Open value          | If `group_type` is `shared_inboxes`: name of a shared inbox (default)<br/>If `group_type` is `workgroups`: workgroup name |
 
 > [!NOTE]
 > In case the name of the `box` is an open value, use option `group_type` set to either `shared_inboxes` or `workgroups`.
@@ -7386,6 +7732,14 @@ If the lookup needs to be only on certain types, you can specify the field: `rec
 {"title":"test title","recipient_types":"user","recipients":["user1@example.com","user2@example.com"]}
 ```
 
+To enable content protection (CSEAR), set parameter `ear_enabled` to `true` in the package creation payload (refer to Faspex package creation API).
+
+The following error is returned by Faspex, if CSEAR was not specified in the package creation and if it is configured as mandatory on the server:
+
+```text
+the provided encryption value (no) does not match the expected server side encryption value (yes)
+```
+
 ### Faspex 5: Send a package with metadata
 
 It's the same as sending a package, but with an extra field `metadata` in the package info.
@@ -7403,14 +7757,14 @@ Option `box` can be used to list packages from a specific box (see [Inbox Select
 
 Option `query` can be used to filter the list of packages, based on native API parameters, directly sent to [Faspex 5 API `GET /packages`](https://developer.ibm.com/apis/catalog/aspera--ibm-aspera-faspex-5-0-api/api/API--aspera--ibm-aspera-faspex-api#getAllPackages).
 
-| Parameter | Type    | Description |
-|-----------|---------|-------------|
-| `offset`  | Native  | Managed by `ascli`: Offset of first package. Default: 0 |
-| `limit`   | Native  | Managed by `ascli`: # of packages per API call. Default: 100 |
-| `q`       | Native  | General search string (case-insensitive, matches if value is contained in several fields) |
-| ...       | Native  | Other native parameters are supported (Refer to API documentation) |
-| `max`     | Special | Maximum number of items to retrieve (stop pages when the maximum is passed) |
-| `pmax`    | Special | Maximum number of pages to request (stop pages when the maximum is passed) |
+| Parameter | Type  | Description |
+|---------|---------|-----------------------------------------------------------------------|
+| `offset`| Native  | Managed by `ascli`: Offset of first package. Default: 0 |
+| `limit` | Native  | Managed by `ascli`: # of packages per API call. Default: 100 |
+| `q`     | Native  | General search string<br/>case-insensitive, matches if value is contained in several fields |
+| ...     | Native  | Other native parameters are supported (Refer to API documentation) |
+| `max`   | Special | Maximum number of items to retrieve (stop pages when the maximum is passed) |
+| `pmax`  | Special | Maximum number of pages to request (stop pages when the maximum is passed) |
 
 A **Command Parameter** in last position, of type `Proc`, can be used to filter the list of packages.
 This advantage of this method is that the expression can be any test, even complex, as it is Ruby code.
@@ -7438,15 +7792,15 @@ By default, paging is used.
 
 Option `query` is available with parameters supported by the API and `ascli` :
 
-| Parameter    | Evaluation   | Description |
-|--------------|--------------|-------------|
-| `paging`     | `ascli`    | Use paging API. Default: `true` |
-| `recursive`  | `ascli`    | List inside folders. Default: `false` |
-| `max`        | `ascli`    | Maximum number of items. |
-| `filter`     | API          | Refer to API doc. Default: `{"basenames":[]}` |
-| `offset`     | API (legacy) | Index of first item. Default: `0` |
-| `limit`      | API (legacy) | Number of items in one API call result. Default: `500` |
-| `per_page`   | API (paging) | Number of items in one API call result. Default: `500` |
+| Parameter | Evaluation   | Default           | Description                             |
+|-----------|--------------|-------------------| ----------------------------------------|
+| `paging`  | `ascli`    | `true`            | Use paging API.                         |
+| `recursive`| `ascli`   | `false`           | List inside folders.                    |
+| `max`     | `ascli`    | -                 | Maximum number of items.                |
+| `filter`  | API          | `{"basenames":[]}`| Refer to API doc.                       |
+| `offset`  | API (legacy) | `0`               | Index of first item.                    |
+| `limit`   | API (legacy) | `500`             | Number of items in one API call result. |
+| `per_page`| API (paging) | `500`             | Number of items in one API call result. |
 
 ### Faspex 5: Content of a received Package
 
@@ -7743,8 +8097,8 @@ A user can receive a package because the recipient is:
 
 As inboxes may be large, it is possible to use the following query parameters:
 
-| Parameter    | Evaluation | Description |
-|--------------|------------|-------------|
+| Parameter    | Evaluation | Description                                                          |
+|--------------|------------|----------------------------------------------------------------------|
 | `count`      | API        | Number of items in one API call result (default=0, equivalent to 10) |
 | `page`       | API        | ID of page in call (default=0) |
 | `startIndex` | API        | Index of item to start (default=0) |
@@ -7887,27 +8241,23 @@ ascli faspex packages recv ALL --once-only=yes --lock-port=12345
 
 ```bash
 address_book
-dropbox list --recipient="*my_dbx"
+dropbox list --recipient='*my_dbx'
 health
 login_methods
 me
-package list --box=sent --query.max=1 --fields=package_id --display=data --format=csv --output=f4_prs2
-package list --query.max=1 --fields=package_id --display=data --format=csv --output=f4_prs1
 package list --query.max=5
-package list --recipient="*my_dbx" --format=csv --fields=package_id --query.max=1 --output=f4_db_id1
-package list --recipient="*my_wkg" --format=csv --fields=package_id --query.max=1 --output=f4_db_id2
-package receive --to-folder=. --link=https://app.example.com/recv_from_user_path
 package receive ALL --once-only=yes --to-folder=. --query=@json:'{"max":10}'
-package receive f4_db_id1 --recipient="*my_dbx" --to-folder=.
-package receive f4_db_id2 --recipient="*my_wkg" --to-folder=.
-package receive f4_pri1 --to-folder=.
-package receive f4_prs2 --to-folder=. --box=sent
-package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["*my_dbx"]}' test_file.bin
-package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["*my_wkg"]}' test_file.bin
-package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal","my_username"]}' test_file.bin
-package send --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE","recipients":["my_email_internal"]}' --remote-source=%name:my_src sample_source.txt
-package send --link=https://app.example.com/send_to_dropbox_path --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin
-package send --link=https://app.example.com/send_to_user_path --delivery-info=@json:'{"title":"$(notdir test) PACKAGE_TITLE_BASE"}' test_file.bin
+package receive f4_db1c --recipient='*my_dbx' --to-folder=.
+package receive f4_db1g --recipient='*my_wkg' --to-folder=.
+package receive f4_pria --to-folder=.
+package receive f4_prs --to-folder=.
+package receive f4_prsc --to-folder=. --box=sent
+package send --delivery-info=@json:'{"title":"package title","recipients":["my_email_internal","my_username"]}' test_file.bin
+package send --delivery-info=@json:'{"title":"package title","recipients":["my_email_internal"]}' --remote-source=%name:my_src sample_source.txt
+package send --delivery-info=@json:'{"title":"package title","recipients":[*my_dbx]}' test_file.bin
+package send --delivery-info=@json:'{"title":"package title","recipients":[*my_wkg]}' test_file.bin
+package send --link=https://app.example.com/send_to_dropbox_path --delivery-info=@json:'{"title":"package title"}' test_file.bin
+package send --link=https://app.example.com/send_to_user_path --delivery-info=@json:'{"title":"package title"}' test_file.bin
 source info %name:my_src --storage=@preset:faspex4_storage
 source list
 source node %name:my_src br / --storage=@preset:faspex4_storage
@@ -7931,17 +8281,17 @@ The payload for creation is the same as for the API, parameters are provided as
 
 Example: Create a Node: Attributes are like API:
 
-| Attribute | Required | Default |
-|-----------|----------|---------|
-| `name`    | Yes      |         |
-| `host`    | Yes      |         |
-| `api_username` | Yes |         |
-| `api_password` | Yes |         |
-| `port`    |          | `9092`  |
-| `ssl`     |          | `true`  |
-| `verify_ssl` |       | `false` |
-| `timeout`    |       | `30s`   |
-| `open_timeout` |     | `10s`   |
+| Attribute    | Required | Default |
+|--------------|----------|---------|
+| `name`       | Yes      |         |
+| `host`       | Yes      |         |
+| `api_username` | Yes    |         |
+| `api_password` | Yes    |         |
+| `port`       |          | `9092`  |
+| `ssl`        |          | `true`  |
+| `verify_ssl` |          | `false` |
+| `timeout`    |          | `30s`   |
+| `open_timeout` |        | `10s`   |
 
 Example: Create a share and add a user to it.
 
@@ -7964,12 +8314,12 @@ ascli shares admin share user_permissions $share_id create @json:'{"user_id":'$u
 admin group all list
 admin node list
 admin share list --fields=DEF,-status,status_message
-admin share user_permissions 1 list
-admin user all app_authorizations 1 modify @json:'{"app_login":true}'
-admin user all app_authorizations 1 show
+admin share user_permissions %name:my_share list
+admin user all app_authorizations %username:my_username modify @json:'{"app_login":true}'
+admin user all app_authorizations %username:my_username show
 admin user all list
-admin user all share_permissions 1 list
-admin user all share_permissions 1 show 1
+admin user all share_permissions %username:my_username list
+admin user all share_permissions %username:my_username show %name:my_share
 admin user ldap add the_name
 admin user local list
 admin user saml import @json:'{"id":"the_id","name_id":"the_name"}'
@@ -7981,10 +8331,10 @@ files download --to-folder=. my_share_folder/test_file.bin my_share_folder/test_
 files mkdir my_share_folder/new_folder
 files sync push /data/local_sync --to-folder=my_share_folder/synctst
 files sync push /data/local_sync --to-folder=my_share_folder/synctst @json:'{"reset":true}'
-files upload --to-folder=my_share_folder 'faux:///testfile?1m' --transfer=httpgw --transfer-info=@json:'{"url":"https://tst.example.com/path@","synchronous":true,"api_version":"v1","upload_chunk_size":100000}'
-files upload --to-folder=my_share_folder sendfolder --transfer=httpgw --transfer-info=@json:'{"url":"https://tst.example.com/path@","synchronous":true,"api_version":"v1","upload_chunk_size":100000}'
+files upload 'faux:///testfile?1m' --to-folder=my_share_folder --transfer=httpgw --transfer-info=@json:'{"url":"https://tst.example.com/path@","synchronous":true,"api_version":"v1","upload_chunk_size":100000}'
 files upload --to-folder=my_share_folder test_file.bin
 files upload --to-folder=my_share_folder test_file.bin --transfer=httpgw --transfer-info=@json:'{"url":"https://tst.example.com/path@"}'
+files upload sendfolder --to-folder=my_share_folder --transfer=httpgw --transfer-info=@json:'{"url":"https://tst.example.com/path@","synchronous":true,"api_version":"v1","upload_chunk_size":100000}'
 health
 ```
 
@@ -8012,7 +8362,7 @@ transfer current list --query.filter='(transfer_name contain aoc)'
 transfer current list --query=@json:'{"filter1":"transfer_name","comp1":"contain","val1":"aoc"}'
 transfer current show console_xfer_id
 transfer smart list
-transfer smart sub my_smart_id @json:'{"source":{"paths":["my_smart_file"]},"source_type":"user_selected"}'
+transfer smart sub my_smart_id @: source.paths.0=my_smart_file source_type=user_selected
 ```
 
 ## Plugin: `orchestrator`:IBM Aspera Orchestrator
@@ -8039,39 +8389,45 @@ workflow status my_workflow_id
 
 ## Plugin: `cos`: IBM Cloud Object Storage
 
-The IBM Cloud Object Storage provides the possibility to execute transfers using FASP.
-It uses the same transfer service as Aspera on Cloud, called Aspera Transfer Service (ATS).
-Available ATS regions: [https://status.aspera.io](https://status.aspera.io)
+IBM Cloud Object Storage supports high-speed transfers using the FASP protocol.
+These transfers leverage the same service used by Aspera on Cloud, called the Aspera Transfer Service (ATS).
+You can check the list of available ATS regions here: <https://status.aspera.io>.
+There are two ways to provide credentials:
+
+- Using existing credentials
 
-There are two possibilities to provide credentials.
-If you already have the endpoint, API key and Resource Instance ID (CRN), use the first method.
-If you don't have credentials but have access to the IBM Cloud console, then use the second method.
+  If you already have the endpoint, API key, and Resource Instance ID (CRN), use this method.
+
+- Using IBM Cloud Console access
+
+  If you do not have credentials but have access to the IBM Cloud Console, use this alternative method.
 
 ### Using endpoint, API key and Resource Instance ID (CRN)
 
-If you have those parameters already, then following options shall be provided:
+If you already have these parameters, provide the following options to `ascli`:
 
-| Option     | Description |
-|------------|-------------|
-| `bucket`   | Bucket name |
+| Option     | Description                                       |
+|------------|---------------------------------------------------|
+| `bucket`   | Bucket name                                       |
 | `endpoint` | Storage endpoint URL<br/>e.g. `https://s3.hkg02.cloud-object-storage.appdomain.cloud` |
-| `apikey`   | API Key     |
-| `crn`      | Resource instance ID |
+| `apikey`   | API Key                                           |
+| `crn`      | Resource instance ID                              |
 
-For example, let us create a default configuration:
+Example: Create a Default Configuration
 
 ```shell
 ascli config preset update mycos --bucket=mybucket --endpoint=https://s3.us-east.cloud-object-storage.appdomain.cloud --apikey=abcdefgh --crn=crn:v1:bluemix:public:iam-identity::a/xxxxxxx
 ascli config preset set default cos mycos
 ```
 
-Then, jump to the [transfer example](#operations-transfers).
+Once configured, proceed to the [transfer example](#operations-transfers).
 
 ### Using service credential file
 
-If you are the COS administrator and don't have yet the credential:
-Service credentials are directly created using the IBM cloud Console (web UI).
-Navigate to:
+If you are the COS administrator and do not yet have credentials,
+you can create them directly from the IBM Cloud Console (Web UI):
+
+Steps:
 
 - &rarr; Navigation Menu
 - &rarr; [Resource List](https://cloud.ibm.com/resources)
@@ -8081,7 +8437,7 @@ Navigate to:
 - &rarr; New credentials (Leave default role: Writer, no special options)
 - &rarr; Copy to clipboard
 
-Then save the copied value to a file, e.g. : `$HOME/cos_service_creds.json`
+Save the copied JSON value to a file, for example: `$HOME/cos_service_creds.json`
 
 or using the IBM Cloud CLI:
 
@@ -8090,9 +8446,10 @@ ibmcloud resource service-keys
 ibmcloud resource service-key _service_key_name_here_ --output JSON|jq '.[0].credentials'>$HOME/service_creds.json
 ```
 
-(if you don't have `jq` installed, extract the structure as follows)
+> [!NOTE]
+> If `jq` is not installed, you can manually extract the credentials section from the JSON output.
 
-It consists in the following structure:
+The service credential file consists of the following structure:
 
 ```json
 {
@@ -8110,33 +8467,32 @@ It consists in the following structure:
 }
 ```
 
-The field `resource_instance_id` is for option `crn`
+The field mappings are as follows:
 
-The field `apikey` is for option `apikey`
+- `resource_instance_id` &rarr; option `crn`
+- `apikey` &rarr; option `apikey`
 
 > [!NOTE]
-> Endpoints for regions can be found by querying the `endpoints` URL from file or from the IBM Cloud Console.
+> Endpoints for regions can be found by querying the `endpoints` URL in the JSON file or from the IBM Cloud Console.
 
 The required options for this method are:
 
-| Option                | Description |
-|-----------------------|-------------|
-| `bucket`              | Bucket name |
-| `region`              | Bucket region<br/>e.g. `eu-de` |
+| Option                | Description                                    |
+|-----------------------|------------------------------------------------|
+| `bucket`              | Bucket name                                    |
+| `region`              | Bucket region<br/>e.g. `eu-de`               |
 | `service_credentials` | JSON information saved from IBM Cloud console. |
 
-For example, let us create a default configuration:
+Example: Create a Default Configuration
 
 ```shell
-ascli config preset update mycos --bucket=laurent --service-credentials=@val:@json:@file:~/service_creds.json --region=us-south
+ascli config preset update mycos --bucket=mybucket --service-credentials=@val:@json:@file:~/service_creds.json --region=us-south
 ascli config preset set default cos mycos
 ```
 
 ### Operations, transfers
 
-Let's assume you created a default configuration from one of the two previous steps (else specify the access options on command lines).
-
-A subset of `node` plugin operations are supported, basically Node API:
+Once you have created a default configuration using one of the previous methods (otherwise, specify the access options directly on the command line), you can perform a subset of `node` plugin operations, which correspond to the Node API.
 
 ```shell
 ascli cos node info
@@ -8144,7 +8500,8 @@ ascli cos node upload 'faux:///sample1G?1g'
 ```
 
 > [!NOTE]
-> A dummy file `sample1G` of size 2 GB is generated using the `faux` PVCL scheme (see previous section and `man ascp`), but you can, of course, send a real file by specifying a real file path instead.
+> The file `sample1G` is a dummy file of size 2 GB, generated using the `faux` PVCL scheme (see previous section and `man ascp`).
+> To upload a real file, simply replace the `faux:///...` URI with the actual file path.
 
 ### Tested commands for `cos`
 
@@ -8173,6 +8530,10 @@ info
 
 ## Plugin: `faspio`: Faspio Gateway
 
+IBM Aspera faspio Gateway is a high-performance proxy that bridges traditional TCP/UDP applications with the Aspera FASP protocol, enabling secure, ultra-fast transfers over any network, even with high latency or packet loss.
+It integrates seamlessly into existing workflows and supports use cases such as server-to-server transfers, database replication, and messaging systems.
+Using `ascli`, you can remotely create and manage bridges on faspio Gateway, simplifying configuration and automation.
+
 ### Tested commands for `faspio`
 
 > [!NOTE]
@@ -8180,7 +8541,7 @@ info
 
 ```bash
 bridges create @json:'{"name":"test1","local":{"protocol":"tcp","tls_enabled":false,"port":"3000","bind_address":"127.0.0.1"},"forward":{"protocol":"fasp","tls_enabled":false,"port":"3994","bind_address":"127.0.0.1","host":["10.0.0.1"]}}'
-bridges delete --bulk=yes @json:@stdin:
+bridges delete --bulk=yes @json:faspio_bclean_list
 bridges list
 health
 ```
@@ -8196,20 +8557,34 @@ Retrieve information on subscription.
 
 ```bash
 entitlement
-health -N
+health
 ```
 
 ## Plugin: `preview`: Preview generator for AoC
 
-The `preview` generates thumbnails (office, images, video) and video previews on storage for use primarily in the Aspera on Cloud application.
-It uses the **Node API** of Aspera HSTS and requires use of Access Keys and its **storage root**.
-Several options can be used to tune several aspects:
+The `preview` plugin is responsible for generating thumbnails (Office documents, images, videos) and video previews on storage, primarily for use within the Aspera on Cloud (AoC) application.
+This plugin leverages the **Node API** of Aspera HSTS and requires:
+
+- An Access Key
+- The associated **storage root**
+
+### Key Features and Options
+
+You can configure several aspects of the preview generation process:
 
-- Methods for detection of new files needing generation
-- Methods for generation of video preview
-- Parameters for video handling
+- File Detection Methods
 
-See also <https://github.com/IBM/aspera-on-cloud-file-previews>
+  Define how new files requiring previews are identified.
+
+- Video Preview Generation Methods
+  
+  Choose the approach for creating video previews (e.g., transcoding options).
+
+- Video Handling Parameters
+  
+  Fine-tune video processing, such as resolution, bitrate, and format.
+
+Using `ascli` is an alternative to <https://github.com/IBM/aspera-on-cloud-file-previews>.
 
 ### Aspera Server configuration
 
@@ -8534,7 +8909,7 @@ If the preview generator does not have access to files on the file system (it is
 check --skip-types=office
 events --once-only=yes --skip-types=office --log-level=info
 scan --scan-id=1 --skip-types=office --log-level=info --file-access=remote --ts=@json:'{"target_rate_kbps":1000000}'
-scan --skip-types=office --log-level=info
+scan --skip-types=office --log-level=info --skip-folder=/special/folder
 show --base=test /etc/hosts
 show --base=test my_docx
 show --base=test my_mpg --video-png-conv=animated
@@ -8561,8 +8936,8 @@ An interface for the `async` utility is provided in the following plugins:
 The `sync` command, available in above plugins, performs the following actions:
 
 - Start a local Sync session by executing the `async` command with the appropriate parameters.
-- Get local Sync session information using the `asyncadmin` command, if available.
 - Get local Sync session information accessing directly the Async snap database.
+- Get local Sync session information using the `asyncadmin` command, if available.
 
 One advantage of using `ascli` over the `async` command line is the possibility to use a configuration file, using standard options of `ascli`.
 Moreover, `ascli` supports sync with application requiring token-based authorization.
@@ -8575,9 +8950,15 @@ Some `sync` parameters are filled by the related plugin using transfer spec para
 
 ### Starting a sync session
 
-To start a sync session, use one of the three sync directions followed by a folder path (remote path for `pull`, local path elsewise).
+To start a sync session, use one of the three sync directions followed by a folder path (remote path for `pull`, local path otherwise).
 The path on the other side is specified using option: `to_folder`.
 
+The general syntax is:
+
+```shell
+ascli ... sync <direction> <path> [<sync_info>] [--to-folder=<path>]
+```
+
 | Direction<br/>(parameter) | Path<br/>(parameter)   | `to_folder`<br/>(option) |
 |-----------|--------|-------------|
 | `push`    | Local  | Remote      |
@@ -8588,6 +8969,11 @@ An optional positional `Hash` argument (`sync_info`) can be provided in either `
 
 A single session can be specified using either formats.
 
+If argument `<sync_info>` is not provided, then a default configuration is generated in the `conf` format as specified in the next sectin.
+
+If argument `<sync_info>` is provided, it defines the format to use.
+If parameter `sessions` or `instance` is present, then `args` is used, else `conf` is used.
+
 #### `sync_info`: `conf` format
 
 This is the **preferred** syntax.
@@ -8595,7 +8981,155 @@ It is the same payload as specified on the `async` option `--conf` or in Node AP
 
 Documentation on Async Node API can be found on [IBM Developer Portal](https://developer.ibm.com/apis/catalog?search=%22aspera%20sync%20api%22).
 
-Parameters `local.path` and `remote.path` are not allowed since they are provided on command line.
+The following parameters are automatically filled from mandatory arguments, and are not allowed:
+
+- `direction`
+- `local.path`
+- `remote.path`
+
+Parameter `name` is set to a default value if not provided in `sync_info`.
+Parameter `quiet` is set to `false` if not provided in `sync_info` and a terminal is detected.
+
+The documentation is available in the terminal with:
+
+```shell
+ascli config sync spec
+```
+
+| Field | Type | Description |
+|------------------------------------------|---------|----------------------------------------------------------------------------------|
+| ascp_dir | string | Directory containing ascp executable to use. |
+| assume_no_mods | boolean | Assume that the directory structure has not been modified.<br/>(`--assume-no-mods`) |
+| checksum | string | Use the specified checksum type. Default is none on cloud storage.<br/>Allowed values: `sha1`, `md5`, `sha1_sparse`, `md5_sparse`, `none`<br/>(`--checksum={enum}`)(-k) |
+| clean_excluded | boolean | Removes any existing entries in the snapshot database for excluded paths<br/>(`--clean-excluded`) |
+| cookie | string | User-defined identification string.<br/>(`--cookie={string}`) |
+| cooloff_max_seconds | integer | Wait up to the specified time for a file to stop changing before skipping synchronization of the file. 0 for disabled<br/>(`--cooloff-max={integer}`) |
+| cooloff_seconds | integer | Delay the start of the transfer to confirm that the content is not changing. Value must be between 0 and 60<br/>(`--cooloff={integer}`) |
+| create_dir | boolean | Create the source directory, target directory, or both, if they do not exist.<br/>(`--create-dir`) |
+| db_cache_size | integer | Specify DB cache size. |
+| db_journal_off | boolean | Turn off DB journal. |
+| db_sync_on | boolean | Enable synchronous write in DB. |
+| dedup | string | Take the specified action when async detects duplicate files on the source.<br/>Allowed values: `copy`, `inode`, `hardlink`, `none`<br/>(`--dedup={enum}`) |
+| delete_before | boolean | Schedule deletes before transfers.<br/>(`--delete-before`) |
+| delete_delay | boolean | Delay actual deletes until the end of the synchronization.<br/>(`--delete-delay`) |
+| direction | string | The direction of replication relative to the local.<br/>Allowed values: `bidi`, `pull`, `push`<br/>(`--direction={enum}`)(-K) |
+| exclude_dirs_older_than | object | Don't scan directories with a recursive modified time older than absolute or async start time - relative_seconds |
+| exclude_dirs_older_than.absolute | string | UTC timestamp. Empty value for disabled. |
+| exclude_dirs_older_than.relative_seconds | integer | Relative to async start time. `-1` for disabled. |
+| filters | array | The filters allow to further specify which files have to be excluded and included from the transfer list. Each filter is defined by a rule and a value. Order of filters matters |
+| filters[].rule | string | The rule for the filter.<br/>Allowed values: `include`, `exclude`, `include_from`, `exclude_from` |
+| filters[].value | string | On include or exclude, the filter's pattern. On include_from or exclude_from, the path containing filter specifications |
+| ignore_delete | boolean | Do not copy removals to the peer.<br/>(`--ignore-delete`) |
+| ignore_mode | boolean | Source files that have had their mode changed after the initial. transfer will not update the destination file mode.<br/>(`--ignore-mode`) |
+| ignore_remote_host_sync_name | boolean | Do not check that the remote host being used for the current. transfer matches the host used when the local database was created |
+| local | object | &nbsp; |
+| local.pass | string | Authenticate the local async with the specified password. |
+| local.path | string | The directory to be synchronized on the local host.<br/>(`--local-dir={string}`)(-d) |
+| local_apply_docroot | boolean | Prepend the docroot to the directory on the local host.<br/>(`--apply-local-docroot`) |
+| local_checksum_threads | integer | Maximum number of threads to do checksum on the local host. Value must be between 1 and 99.<br/>(`--local-checksum-threads={integer}`) |
+| local_db_dir | string | Use the specified database directory on the local host. Default is `.private-asp` at the root level of the synchronized directory.<br/>(`--local-db-dir={string}`)(-b) |
+| local_db_store_dir | string | Store/Restore the database to/from the specified directory on the local host. The value can be an absolute path, an URI or - (use the local sync dir)<br/>(`--local-db-store-dir={string}`) |
+| local_force_stat | boolean | Forces the local async to retrieve file information even when no changes are detected by the scanner or monitor.<br/>(`--local-force-stat`) |
+| local_fs_threads | integer | Maximum number of threads to do file system operations on the local host. Value must be between 1 and 99.<br/>(`--local-fs-threads={integer}`) |
+| local_keep_dir | string | Move deleted files into the specified directory on the local host.<br/>(`--keep-dir-local={string}`) |
+| local_mount_signature | string | Verify that the file system is mounted by the existence of this file on the local host.<br/>(`--local-mount-signature={string}`) |
+| local_move_cache_timeout_seconds | integer | Delay in seconds before aborting moving a file from local cache to final destination. `-1` for disabled.<br/>(`--local-move-cache-timeout={integer}`) |
+| local_preserve_acls | string | Preserve access control lists on the local host.<br/>Allowed values: `native`, `metafile`, `none`<br/>(`--preserve-acls={enum}`) |
+| local_preserve_xattrs | string | Preserve extended attributes on the local.<br/>Allowed values: `native`, `metafile`, `none`<br/>(`--preserve-xattrs={enum}`) |
+| local_scan_interval_milliseconds | integer | Enable periodic scans on the local host during a continuous sync. `-1` for disabled<br/>(`--scan-interval={integer}`) |
+| local_scan_threads | integer | Number of directory scanning threads on the local host. Value must be between 1 and 99<br/>(`--scan-threads={integer}`) |
+| local_stat_cache_size | integer | Set stat cache size on the local host. 0 for disabled. |
+| log | object | &nbsp; |
+| log.level | string | Use the specified log level.<br/>Allowed values: `log`, `dbg1`, `dbg2`<br/>(special:`-D`) |
+| log.local_dir | string | Use the specified logging directory on the local host.<br/>(`--alt-logdir={string}`)(-L) |
+| log.remote_dir | string | Use the specified logging directory on the remote host.<br/>(`--remote-logdir={string}`)(-R) |
+| manifest_path | string | A directory path where ascp will create manifest TEXT files (passed to ascp as --file-manifest-path) |
+| mirror | boolean | Force the pulling side to be exactly like the pushing side, removing files on the destination that don't exist on the source and resending source files that don't have an exact match on the destination. Cannot be used in bi-directional mode.<br/>(`--mirror`) |
+| mode | string | Specify whether async runs continuously or not. In `one_time` mode, async stops after the first full synchronization. `continuous` supported only if the source is Windows or Linux.<br/>Allowed values: `one_time`, `continuous`<br/>(special:`--continuous`)(-C) |
+| monitor_buffer_size | integer | Bytes to allocate for the change monitor buffer. Applies to any Windows machine on either side. `-1` to use the computed value. |
+| name | string | Name of the synchronization pair.<br/>(`--name={string}`)(-N) |
+| no_log | string | Suppress log messages for ITEM. The only currently supported ITEM is 'stats', which suppresses both STATS and PROG log messages.<br/>(`--no-log={string}`) |
+| no_preserve_root_attrs | boolean | Disable the preservation of attributes on the Sync root.<br/>(`--no-preserve-root-attrs`) |
+| no_scan | boolean | Skip initial scanning.<br/>(`--no-scan`) |
+| notifications_sharing_retry_max | integer | Retry processing filesystem notifications up to the specified maximum number after a sharing violation. |
+| overwrite | string | Overwrite files according to the specified policy. Default is determined by the direction: `conflict` for `bidi`, otherwise `always`.<br/>Allowed values: `always`, `older`, `conflict`<br/>(`--overwrite={enum}`)(-o) |
+| pending_max | integer | Allow the maximum number of files that are pending transfer to be no more than the specified number.<br/>(`--pending-max={integer}`) |
+| preserve_access_time | boolean | Preserve file access time from the source to the destination.<br/>(`--preserve-access-time`) |
+| preserve_creation_time | boolean | Preserve file creation time from the source to the destination.<br/>(`--preserve-creation-time`) |
+| preserve_gid | boolean | Preserve the file owner's GID.<br/>(`--preserve-gid`)(-j) |
+| preserve_modification_time | boolean | Preserve file modification time from the source to the destination.<br/>(`--preserve-modification-time`) |
+| preserve_object_lock_legal_hold | boolean | Preserve object lock legal hold status from the source to the destination.<br/>(`--preserve-object-lock-legal-hold`) |
+| preserve_object_lock_retention | boolean | Preserve object lock retention from the source to the destination.<br/>(`--preserve-object-lock-retention`) |
+| preserve_object_metadata | boolean | Preserve object metadata from the source to the destination.<br/>(`--preserve-object-metadata`) |
+| preserve_uid | boolean | Preserve the file owner's UID.<br/>(`--preserve-uid`)(-u) |
+| quiet | boolean | Disable progress display.<br/>(`--quiet`)(-q) |
+| remote | object | &nbsp; |
+| remote.connect_mode | string | Define how to connect to the remote.<br/>Allowed values: `ssh`, `ws`<br/>(special:`--ws-connect`) |
+| remote.fingerprint | string | Check it against server SSH host key fingerprint. |
+| remote.host | string | Use the specified host name or address of the remote host.<br/>(`--host={string}`) |
+| remote.pass | string | Authenticate the transfer with the specified password.<br/>(`--pass={string}`)(-w) |
+| remote.path | string | Synchronize the specified directory on the remote host.<br/>(`--remote-dir={string}`)(-r) |
+| remote.port | integer | Use the specified TCP port for SSH. Used when connect_mode is `ssh`<br/>(`--tcp-port={integer}`)(-P) |
+| remote.private_key_paths | array | Authenticate with the specified SSH private key file.<br/>(`--private-key-path={array}`)(-i) |
+| remote.proxy | object | Specify the address of the Aspera high-speed proxy server.<br/>(special:`--proxy={object}`) |
+| remote.proxy.host | string | Use the specified host name or address of the proxy. |
+| remote.proxy.pass | string | Authenticate to the proxy with the specified password. |
+| remote.proxy.port | integer | Use the specified port, default is 9091 for dnat, 9092. for dnats |
+| remote.proxy.protocol | string | The protocol to be used.<br/>Allowed values: `none`, `dnat`, `dnats` |
+| remote.proxy.user | string | Authenticate to the proxy with the specified username. |
+| remote.token | string | Token string passed to server's authentication service. |
+| remote.token_node_user | string | Node API user identity associated with the token. Required for node user bearer tokens |
+| remote.user | string | Authenticate the transfer with the specified username.<br/>(`--user={string}`) |
+| remote.ws_port | integer | Use the specified port for Websocket. Used when connect_mode is `ws`. |
+| remote_checksum_threads | integer | Maximum number of threads to do checksum on the remote host. Value must be between 1 and 99<br/>(`--remote-checksum-threads={integer}`) |
+| remote_db_dir | string | Use the specified database directory on the remote host. Default is `.private-asp` at the root level of the synchronized directory.<br/>(`--remote-db-dir={string}`)(-B) |
+| remote_db_store_dir | string | Store/Restore the database to/from the specified directory on the remote host. The value can be an absolute path, an URI or - (use the remote sync dir).<br/>(`--remote-db-store-dir={string}`) |
+| remote_force_stat | boolean | Forces the remote async to retrieve file information even when no changes are detected by the scanner or monitor.<br/>(`--remote-force-stat`) |
+| remote_fs_threads | integer | Maximum number of threads to do file system operations on the remote host. Value must be between 1 and 99.<br/>(`--remote-fs-threads={integer}`) |
+| remote_keep_dir | string | Move deleted files into the specified directory on the remote host.<br/>(`--keep-dir-remote={string}`) |
+| remote_mount_signature | string | Verify that the file system is mounted by the existence of this file on the remote host.<br/>(`--remote-mount-signature={string}`) |
+| remote_move_cache_timeout_seconds | integer | Delay in seconds before aborting moving a file from remote cache to final destination. `-1` for disabled.<br/>(`--remote-move-cache-timeout={integer}`) |
+| remote_preserve_acls | string | Preserve access control lists on the remote host. If not specified, the default behavior is to use the same storage mode as specified by `preserve_acls`.<br/>Allowed values: `native`, `metafile`, `none`<br/>(`--remote-preserve-acls={enum}`) |
+| remote_preserve_xattrs | string | Preserve extended attributes on the remote host. If not specified, the default behavior is to use the same storage mode as specified by `preserve_xattrs`.<br/>Allowed values: `native`, `metafile`, `none`<br/>(`--remote-preserve-xattrs={enum}`) |
+| remote_scan_interval_milliseconds | integer | Enable periodic scans on the remote host. `-1` for disabled.<br/>(special:`--remote-scan-interval={integer}`) |
+| remote_scan_threads | integer | Number of directory scanning threads on the remote host. Value must be between 1 and 99.<br/>(`--remote-scan-threads={integer}`) |
+| remote_stat_cache_size | integer | Set stat cache size on the remote host. 0 for disabled. |
+| remove_after_transfer | boolean | Remove source files after they are successfully synchronized.<br/>(`--remove-after-transfer`) |
+| reset | boolean | Clear the snapshot database and rescan the synchronized directories and files to create a fresh snapshot<br/>(`--reset`)(-x) |
+| resume | object | Partial transfers may exist if communication disruptions caused the underlying ascp processes to terminate early. Note that transfer resumption can only happen if the `reset` option is disabled. If an async session starts with `reset` enabled and resume enabled, transfers interrupted during that session will be resumeable, but only if async is then restarted with 'reset' disabled. |
+| resume.enabled | boolean | Enable the possibility of resuming individual file transfers between async sessions. |
+| resume.max_age | integer | Sets the age limit in days for temporary files that will be preserved on cleanup (usually at async's start and stop) for potential transfer resume. Temp files older than the given value will be removed regardless of whether they might be resumeable.<br/>(`--resume-age-days={integer}`) |
+| resume.min_size | integer | This field specifies the minimum size of files that will be allowed to resume.<br/>(`--support-resume={integer}`) |
+| resume_scan | boolean | Resume the scan from where the previous execution left off.<br/>(`--resume-scan`) |
+| scan_dir_rename | boolean | Enable the detection of renamed directories and files compared. to the previous scan, based on matching inodes<br/>(`--scan-dir-rename`) |
+| scan_file_rename | boolean | Enable the detection of renamed files compared to the previous scan, based on matching inodes.<br/>(`--scan-file-rename`) |
+| scan_intensity | string | Scan at the set intensity. `vlow` minimizes system activity. `vhigh` maximizes system activity by continuously scanning files without rest.<br/>Allowed values: `vlow`, `low`, `medium`, `high`, `vhigh`<br/>(`--scan-intensity={enum}`)(-H) |
+| sharing_retry_max | integer | Retry synchronizations up to the specified maximum number after a sharing violation.<br/>(`--sharing-retry-max={integer}`) |
+| store_metadata_records | boolean | Store the acls or xattrs in the snapshot database.<br/>(`--store-metadata-records`) |
+| symbolic_links | string | Handle symbolic links with the specified method. Default is `skip` on windows, `copy` otherwise.<br/>Allowed values: `copy`, `skip`, `follow`<br/>(`--symbolic-links={enum}`)(-n) |
+| tags | object | User-defined metadata tags.<br/>(special:`--tags64={object}`) |
+| transfer_threads | array | Use the specified number of dedicated transfer threads to process files smaller or equal to the specified size<br/>(special:`--transfer-threads={array}`) |
+| transfer_threads[].size | integer | Upper limit. `-1` for infinity. |
+| transfer_threads[].threads | integer | The number of threads. |
+| transport | object | &nbsp; |
+| transport.cipher | string | Specify encryption algorithm for file data.<br/>Allowed values: `none`, `aes128`, `aes192`, `aes256`, `aes128cfb`, `aes192cfb`, `aes256cfb`, `aes128gcm`, `aes192gcm`, `aes256gcm`<br/>(`--cipher={enum}`)(-c) |
+| transport.compression | string | Compress a file before transfer using the specified MODE.<br/>Allowed values: `none`, `zlib`<br/>(`--compression={enum}`) |
+| transport.datagram_size | integer | Specify the datagram size (MTU) for FASP. By default it uses the detected path MTU.<br/>(`--datagram-size={integer}`)(-Z) |
+| transport.min_rate | integer | Attempt to transfer no slower than the specified rate (in bps).<br/>(`--min-rate={integer}`)(-m) |
+| transport.rate_policy | string | Defines how `ascp` will manage the bandwidth.<br/>Allowed values: `fair`, `fixed`, `high`, `low`<br/>(`--rate-policy={enum}`)(-a) |
+| transport.raw_options | array | Pass arbitrary arguments to `ascp`.<br/>(special:`--raw-options={array}`) |
+| transport.read_block_size | integer | Use the specified block size (in bytes) for reading. Default is determined by `aspera.conf`.<br/>(`--read-block-size={integer}`)(-g) |
+| transport.rexmsg_size | integer | Use the specified size (in bytes) for a retransmission request. Default is determined by `aspera.conf`.<br/>(`--rexmsg-size={integer}`)(-X) |
+| transport.target_rate | integer | Transfer no faster than the specified rate (in bps).<br/>(`--target-rate={integer}`)(-l) |
+| transport.udp_port | integer | Use the specified UDP port for FASP data transfer.<br/>(`--udp-port={integer}`)(-O) |
+| transport.write_block_size | integer | Use the specified block size (in bytes) for writing. Default is determined by `aspera.conf`.<br/>(`--write-block-size={integer}`)(-G) |
+| watchd | object | When connection is configured, `asperawatchd` is used to detect the changes on the source directory.<br/>(special:`--watchd={object}`) |
+| watchd.datastore | string | Specify the type of datastore, `none` for disabled.<br/>Allowed values: `none`, `redis`, `scalekv` |
+| watchd.domain | string | Specify the domain. Default is the current username. |
+| watchd.host | string | Use the specified host name or address to connect to the datastore. |
+| watchd.port | integer | Use the specified port. |
+| write_gid | string | Try to write files as the specified group.<br/>(`--write-gid={string}`) |
+| write_uid | string | Try to write files as the specified user.<br/>(`--write-uid={string}`) |
 
 #### `sync_info`: `args` format
 
@@ -8606,19 +9140,39 @@ Technically, it allows definition of multiple sync sessions in a single command,
 
 This is the mode selection if there are either keys `sessions` or `instance` in option `sync_info`.
 
-Parameters `local_dir` and `remote_dir` are not allowed since they are provided on command line.
+The following parameters are automatically filled from mandatory arguments, and are not allowed:
 
-### Sync management and monitoring
+- `direction`
+- `local_dir`
+- `remote_dir`
 
-The `admin` command provides several sub commands:
+Parameter `name` is set to a default value if not provided in `sync_info`.
 
-- `status`: Uses the utility `asyncadmin`, available only on server products.
-- Other commands access directly the Async snap database (`snap.db`).
+### Sync management and monitoring: `admin`
 
-For those commands, the user must provide the path to the database folder, i.e. a folder containing a subfolder named `.private-asp`.
-By default it is the local synchronized folder.
-If this folder contains only one session information (i.e. a folder containing the `snap.db` file), it will be used by default.
-Else, the user must specify a session name in the optional `Hash`, in `name`.
+The `admin` command provides several sub commands that access directly the Async snap database (`snap.db`).
+(With the exception of `status` which uses the utility `asyncadmin`, available only on server products.)
+
+This command does not require any communication to the server and accesses only the local database.
+It can be executed also from the `config` plugin:
+
+```shell
+ascli config sync admin
+```
+
+To use the `admin` command, the gem `sqlite3` shall be installed:
+
+```shell
+gem install sqlite3
+```
+
+In order to use the `admin` commands, the user must provide the path to the database folder:
+
+- i.e. a folder containing a subfolder named `.private-asp`.
+- By default it is the local synchronized folder.
+- If an alternate folder is specified for the database, then specify it.
+- If this folder contains only one session information (i.e. a folder containing the `snap.db` file), it will be used by default.
+- Else, the user must specify a session name in the optional `Hash`, in the `name` key.
 
 ## Hot folder
 
@@ -8757,17 +9311,17 @@ This is done with option `smtp`.
 The `smtp` option is a `Hash` (extended value) with the following fields:
 
 <!-- markdownlint-disable MD034 -->
-| Field        | Default             | Example                    | Description                      |
-|--------------|---------------------|----------------------------|----------------------------------|
-| `server`     | -                   | `smtp.gmail.com`           | SMTP server address              |
-| `tls`        | `true`              | `true`                     | Enable `STARTTLS` (port 587)     |
-| `ssl`        | `false`             | `false`                    | Enable `TLS` (port 465)          |
-| `port`       | `587` or `465` or `25` | `587`                   | Port for service                 |
-| `domain`     | _domain of server_  | gmail.com                  | Email domain of user             |
-| `username`   | -                   | john@example.com           | User to authenticate on SMTP server, leave empty for open auth. |
-| `password`   | -                   | my_password_here           | Password for above username      |
-| `from_email` | username if defined | johnny@example.com         | Address used if receiver replies |
-| `from_name`  | same as email       | John Wayne                 | Display name of sender           |
+| Field        | Default            | Example          | Description                      |
+|--------------|--------------------|------------------|----------------------------------|
+| `server`     | -                  | `smtp.gmail.com` | SMTP server address              |
+| `tls`        | `true`             | `true`           | Enable `STARTTLS` (port 587)     |
+| `ssl`        | `false`            | `false`          | Enable `TLS` (port 465)          |
+| `port`       | `587`<br/>`465`<br/>`25` | `587`  | Port for service                 |
+| `domain`     | _domain of_ `server` | gmail.com      | Email domain of user             |
+| `username`   | -                  | john@example.com | User to authenticate on SMTP server<br/>Leave empty for open auth. |
+| `password`   | -                  | my_password_here | Password for above username      |
+| `from_email` | username if defined|johnny@example.com| Address used if receiver replies |
+| `from_name`  | same as email      | John Wayne       | Display name of sender           |
 <!-- markdownlint-enable MD034 -->
 
 ### Example of configuration
@@ -8873,22 +9427,23 @@ During execution, it generates all low level events, one per line, in JSON forma
 
 Top level parameters supported by `asession`:
 
-| Parameter  | Description |
-|------------|-------------|
-| `spec`     | The [**transfer-spec**](#transfer-specification)    |
-| `agent`    | Same parameters as transfer-info for agent `direct` |
-| `loglevel` | Log level of `asession`                             |
-| `file_list_folder` | The folder used to store (for garbage collection) generated file lists.<br/>By default, it is `[system tmp folder]/[username]_asession_filelists` |
+| Parameter          | Description                                                            |
+|--------------------|------------------------------------------------------------------------|
+| `spec`             | The [**transfer-spec**](#transfer-specification)                       |
+| `agent`            | Same parameters as transfer-info for agent `direct`                    |
+| `loglevel`         | Log level of `asession`                                                |
+| `file_list_folder` | The folder used to store (for garbage collection) generated file lists.<br/>Default: `[system tmp folder]/[username]_asession_filelists` |
 
 ### Comparison of interfaces
 
-| feature/tool          | Transfer Daemon | FASPManager                      | `ascp` | `asession` |
-|-----------------------|--------------|---------------------------------|--------|------------|
-| language integration  | Many         | C/C++<br/>C#/.net<br/>Go<br/>Python<br/>java<br/> | Any    | Any        |
-| required additional components to `ascp` | Daemon       | Library<br/>(+headers) | - | Ruby<br/>Aspera gem |
-| startup               | Daemon       | API | Command line arguments | JSON on stdin<br/>(standard APIs:<br/>JSON.generate<br/>Process.spawn) |
-| events                | Poll     | Callback | Possibility to open management port<br/>and proprietary text syntax | JSON on stdout |
-| platforms             | Any with `ascp` and transfer daemon | Any with `ascp` (and SDK if compiled) | Any with `ascp` | Any with Ruby and `ascp` |
+| Feature/Tool | Transfer Daemon | FASPManager | `ascp` | `asession` |
+|------------|-------------|-------------|-------------|-------------|
+| status | Supported | Deprecated | Supported | Deprecated |
+| language integration | Many | C/C++<br/>C#/.net<br/>Go<br/>Python<br/>java<br/> | Any | Any |
+| required additional components to `ascp` | Daemon | Library<br/>(+headers) | - | Ruby<br/>Aspera gem |
+| startup | Daemon | API | Command line arguments | JSON on stdin<br/>(standard APIs:<br/>JSON.generate<br/>Process.spawn) |
+| events | Poll | Callback | Possibility to open management port<br/>and proprietary text syntax | JSON on stdout |
+| platforms | Like `ascp` and `transferd` | Like `ascp` and lib (if compiled) | Any with `ascp` | Any with Ruby and `ascp` |
 
 ### Simple session
 
@@ -9024,24 +9579,30 @@ This also requires Ruby header files.
 If Ruby was installed as a Linux Packages, then also install Ruby development package:
 `ruby-dev` or `ruby-devel`, depending on distribution.
 
-### ED25519 key not supported
+### Private key type: `ed25519` not supported by default
 
-ED25519 keys are deactivated since `ascli` version 0.9.24 as it requires additional gems that require native compilation and thus caused problems.
-This type of key will just be ignored.
+There are a few aspects concerning ED25519 keys.
 
-To re-activate, set env var `ASCLI_ENABLE_ED25519` to `true`.
+By default, the `aspera-cli` gem does not depend on the `ed25519` gem because it requires compilation of native code which can cause problems and prevent the installation of `ascli`, especially when using JRuby.
+Refer to [this](https://github.com/net-ssh/net-ssh/issues/565).
+If you want to use `ed25519` keys, then install the required gems:
 
-Without this deactivation, if such key was present in user's `.ssh` folder then the following error was generated:
+```shell
+gem install ed25519 bcrypt_pbkdf
+```
+
+In addition, if those two gems are not installed, and if you are using Private Keys encoded using the OpenSSH format, then you'll get the message:
 
 ```text
-OpenSSH keys only supported if ED25519 is available
+OpenSSH keys only supported if ED25519 is available (NotImplementedError)
+net-ssh requires the following gems for ed25519 support:
+ * ed25519 (>= 1.2, < 2.0)
+ * bcrypt_pbkdf (>= 1.0, < 2.0)
+See https://github.com/net-ssh/net-ssh/issues/565 for more information
 ```
 
-Which meant that you do not have Ruby support for ED25519 SSH keys.
-You may either install the suggested Gems, or remove your ed25519 key from your `.ssh` folder to solve the issue.
-
-In addition, host keys of type: `ecdsa-sha2` and `ecdh-sha2` are also deactivated by default.
-To re-activate, set env var `ASCLI_ENABLE_ECDSHA2` to `true`.
+In addition, if **JRuby** is used, host keys of type: `ecdsa-sha2` and `ecdh-sha2` are also deactivated by default.
+To activate, set env var `ASCLI_ENABLE_ECDSHA2` to `true`.
 
 ### JRuby: `net-ssh`: Unsupported algorithm
 
@@ -9068,11 +9629,11 @@ To deactivate this error, enable option `IGNORE_UNEXPECTED_EOF` for `ssl_options
 --http-options=@json:'{"ssl_options":["IGNORE_UNEXPECTED_EOF"]}'
 ```
 
-### Error: `ascp`: /lib64/libc.so.6: version `GLIBC_2.28' not found
+### Error: `ascp`: `/lib64/libc.so.6`: version `GLIBC_2.28` not found
 
 This happens on Linux x86 if you try to install `transferd` on a Linux version too old to support a newer `ascp` executable.
 
-Workaround: Install an older version:
+Workaround: Install an older version of `transferd`:
 
 ```shell
 ascli config transferd install 1.1.2