Pass a CLI credential without printing it

Pass a CLI credential without printing it is easier to verify when you use one controlled item and confirm the account, workspace, source, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

• Open a terminal running the Dosya CLI in the current released client.
• Confirm the active account and workspace, then identify restricted automation credential in a secret store.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery codes, private links, personal data, and confidential file contents out of screenshots and support messages.

Steps: pass a CLI credential without printing it

1. Open a terminal running the Dosya CLI and confirm the active account and workspace.
2. Locate restricted automation credential in a secret store and verify its name or identifying details.
3. Load it through the documented protected input or environment mechanism, disable shell tracing, and avoid command-line history.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that the CLI authenticates while logs and process arguments remain free of the secret.
6. Refresh, fetch, or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and the CLI authenticates while logs and process arguments remain free of the secret. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, policy, and selected integration surface.
• Processing, indexing, background transfer, provider authorization, or storage accounting can delay a visible result.
• For destructive, access-changing, or automated actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to a terminal running the Dosya CLI, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error, delivery, or request identifier.

Related guides

• Authenticate the Dosya CLI
• Use CLI JSON output