Skip to content

Adal CLI v1.0.3

Choose a tag to compare

@github-actions github-actions released this 11 Nov 23:40
· 3 commits to main since this release

Adal CLI v1.0.3

Adal CLI now supports HTTP Tunnel. Forward requests from a public Adal Cloud URL to an HTTP or HTTPS endpoint reachable from the machine running the CLI. HTTP Tunnel is available in SE, DE, and KZ.

Get started

  1. Create a Tunnel in the Adal Cloud Dashboard and set its endpoint URL, for example http://127.0.0.1:8080.
  2. Create a CLI token on the Tunnel page.
  3. Start the CLI with that token.
./adal-cli --token <tunnel-token>

On Windows, run .\adal-cli.exe --token <tunnel-token> in PowerShell. Once the CLI is connected, send a request to the public URL shown in the Dashboard. You can view the exchange in Tunnel requests.

What’s new

  • Requests and responses stream in both directions, with support for concurrent exchanges.
  • The CLI preserves escaped paths, query strings, repeated headers, and compressed body bytes.
  • The CLI reconnects after temporary connection failures. A disconnect cancels in-flight exchanges without replaying them. Disabling or deleting a Tunnel stops the CLI session.

Upgrading

The CLI selects Inbound or Tunnel automatically from the token. If your Inbound token was revoked during the rollout, create a new token on your Inbound channel and restart the CLI.

Release archives cover Linux, macOS, and Windows on amd64 and arm64. SHA-256 checksums are provided in checksums.txt.