Skip to content
ayx-rsv0.22.1

v0.17.0-internal.1

Internal Windows and WSL2/Linux evaluation release.

This release makes the Wizard email-OTP authentication flow the default for ayx one login. The Legacy email-OTP flow remains available as an explicit rollback path:

ayx one login --auth-flow legacy

The equivalent environment override remains available for automation: AYX_AUTH_ROLLOUT=legacy.

First-time setup

Section titled “First-time setup”

  1. Extract the platform artifact, put the included ayx/ayx.exe on your PATH, and run ayx onboard.

  2. Paste the Alteryx One workspace URL when prompted.

  3. Choose Log in now.

  4. Enter the emailed one-time passcode and workspace password. After a successful interactive login, accept the default Save this workspace password securely for future logins? [Y/n] prompt if this profile should reuse the password on future logins.

  5. Verify the connection:

    ayx one auth status
    ayx one workspace current

Credentials use the operating-system secure store by default. Plaintext profile storage is an explicit, affirmative fallback and should not be used for ordinary internal workspaces. The standalone login command does not offer session-only credentials because its process ends after the login completes.

When no profile flags are supplied, ayx uses the active profile pointer (or the central default profile if no pointer exists). An explicit --profile wins, followed by AYX_PROFILE. The Wizard rollout and secure persistence are also the defaults; --auth-flow legacy remains an explicit rollback option.

Recovery

Section titled “Recovery”

Do not automatically retry a login when the CLI says an OTP send or PAT mint may have committed. Preserve the profile and inspect the redacted error. If a fresh login is required, use the independently characterized Legacy flow:

ayx one login --auth-flow legacy

Do not send OTPs, passwords, tokens, profile files, or keyring exports with a support report. Include the version, operating system, command, rollout selection, and redacted error text instead.

Platform scope

Section titled “Platform scope”

This internal release is a target-platform evaluation build for native Windows and WSL2/Linux. Existing test-profile live authentication and native keyring signoff are required before broad internal distribution. Apple/macOS validation and distribution are deferred.