dcloud iam cli-auth-policy dry-run

Show who and what a proposed policy would affect, changing nothing

IAM iam:GetCliAuthPolicyRead

Lists people with neither a passkey nor a Touch ID device key, personal access keys that would be refused, unverified CLI sessions that would stop, and machine keys (never affected).

Synopsis

dcloud iam cli-auth-policy dry-run --require-passkey-cli requirePasskeyCli --personal-key-max-age-days personalKeyMaxAgeDays [flags]

Flags

  • --require-passkey-cliRequired

    boolean (--require-passkey-cli / --no-require-passkey-cli)

    People's CLI sessions must be opened with Touch ID or a passkey, sensitive commands ask for a fresh confirmation once the person's confirmation window has passed, and older CLIs can no longer sign in with a 90-day access key. Service accounts and role sessions are never affected

  • --personal-key-max-age-daysRequired

    number

    People's own access keys: null = no restriction, 0 = refused, N = refused once older than N days (at most 3650). Keys of service accounts and role sessions, and keys with a scope policy, are never refused

    Constraints: integer, 0-3650

    May be null.

  • --cli-step-up-max-minutesOptional

    object

    The longest a Touch ID or passkey confirmation may last for people of this organization, in minutes: 1, 2, 5, 10, 15, 30 or 60 (each person chooses 5 to 60, 5 by default). null: no cap below 60. Left out: unchanged

    Constraints: JSON

    May be null.

Example

dcloud iam cli-auth-policy dry-run --require-passkey-cli --personal-key-max-age-days 1

Generated from the API description, the same one the API checks requests against and the CLI is built from.