Exec¶
Use the exec command to run commands on available services (the available services depend on the authorized user's account).
Shorthand
The exec subcommand may be omitted. Service commands can be invoked directly by specifying the service name after idsec. Both forms are equivalent:
| Full form | Shorthand |
|---|---|
idsec exec sia sso short-lived-password |
idsec sia sso short-lived-password |
idsec exec pcloud safes create --safe-name=safe |
idsec pcloud safes create --safe-name=safe |
SIA services¶
The following SIA commands are supported:
idsec exec sia: Root command for the SIA service (aliases: dpa)sso- SSO end-user operationsk8s- Kubernetes servicedb- DB serviceworkspaces- Workspaces servicetarget-sets- Target sets operationsdb- Database operationssecrets- Secrets servicevm- VM operationsdb- Database operationsaccess- Access servicessh-ca- SSH CA key serviceshortened-connection-string- Shortened connection string servicesettings- Settings servicecertificates- Certificates service
idsec exec cmgr: Root command for the CMGR service (aliases: connectormanager,cm)idsec exec pcloud: Root command for PCloud service (aliases: privilegecloud,pc)accounts- Accounts managementsafes- Safes managementplatforms- Platforms managementapplications- Applications management
idsec exec identity: Root command for the Identity service (aliases: idaptive,id)directories- Directories managementusers- Users managementroles- Roles managementauth-profiles- Auth profiles managementpolicies- Policies management
idsec exec sechub: Root command for the Secrets Hub Service (aliases: secretshub,sh)configuration- Configuration managementservice-info- Service Info managementsecrets- Secrets managementscans- Scans managementsecret-stores- Secret Stores managementsync-policies- Sync Policies management
idsec exec sm: Root command for the SM service (aliases: sessionmonitoring)idsec exec policy: Root command for the Policy service (aliases: accesspolicies, acp)cloud-access- Cloud Console managementdb- SIA DB managementvm- SIA VM management
All commands have their own subcommands and respective arguments and aliases.
Running¶
idsec exec
Paging long list output¶
Use --page-size when a command returns a long list and you want to browse the result in the terminal.
idsec policy cloud-access list-policies --profile-name myprofile --page-size 10
When --page-size is set and the command is running in an interactive terminal, the CLI prints exactly that number of items and waits for a keypress:
- Press
spaceorEnterto show the next page. - Press
q,Esc,Ctrl+C, orCtrl+Dto stop paging.
The pager controls only page boundaries and continue/quit behavior. Item rendering stays with command output formatting (currently pretty JSON for these list results). Between pages, output is appended so you can scroll up to previous pages.
Paging is client-side only. The CLI still receives the SDK result and only controls interactive paging flow. When output is piped or redirected, the interactive pager is disabled and the CLI writes a JSON array so commands remain scriptable:
idsec policy cloud-access list-policies --profile-name myprofile --page-size 10 | jq '.'
Search is not built into the interactive pager. For searching or filtering, pipe the command output to tools such as less, grep, or jq:
idsec policy cloud-access list-policies --profile-name myprofile | less
Usage¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 | |