Secrets Manager Token Add
Secrets Manager — Token Add
The secrets-manager token add subcommand adds a one-time access token to an existing KSM application. It is a discoverable shortcut to the secrets-manager client add flow, designed for operators and automation scripts that need to provision tokens without re-creating the application.
Applies to: Keeper Commander 17.3+
Syntax
secrets-manager token add <APP_UID_OR_NAME> [options]This is equivalent to:
secrets-manager client add --app <APP_UID_OR_NAME> [options]Both commands produce identical output. token add exists for discoverability — the help text for secrets-manager now surfaces a dedicated token sub-group.
Parameters
<APP_UID_OR_NAME>
Yes
UID or name of an existing KSM application
Options
--count <n>
integer
1
Number of one-time tokens to generate
--unlock-ip
flag
false
Remove the IP-lock restriction from the generated token
--first-access-expires-in-min <n>
integer
—
Minutes until the token expires if not used for the first time
--access-expire-in-min <n>
integer
—
Minutes until the token expires after first use
--name <label>
string
—
Friendly name for the generated client
--config-init <type>
string
—
Output format for config initialisation (k8s, json, b64)
--return-tokens
flag
false
Return raw token string(s) to the caller (for scripting)
Examples
Add a single token to an application
Generate multiple tokens
Generate a token that expires in 30 minutes if unused
Scripting — capture the token value
Generate a token with Kubernetes config output
Notes
The application must already exist. To create a new KSM application, use
secrets-manager app create <NAME>.Tokens generated with
--unlock-ipare not bound to the IP address of the machine that generated them.--return-tokensis intended for use in scripts. Without it, the token is printed to stdout as part of the normal command output.Implementation delegates entirely to
KSMCommand.add_client()— no new API surface is introduced.
Last updated

