Quick Summary: The IAM Engineer Command-Line Interface from Oleria, an AI-native identity security & governance platform, gives terminal-native engineers a first-class CLI to query, investigate, and automate identity work without ever leaving the shell — replacing hand-built API wrappers with a supported, pipe-friendly tool.
Command-line tool for the IAM engineer's daily work.
Query, investigate, modify, report — from the terminal. For when the GUI isn't where the work happens.
IAM engineers who live in the terminal lose context every time they have to switch to a GUI. Investigations interleave with grep, with kubectl, with cloud CLIs; switching to a browser to query the identity tool breaks the flow. The good engineers either work around it (with hand-built API wrappers) or accept the productivity hit.
A good CLI is its own work: command structure that fits the operator's mental model, output formats suitable for piping, authentication that respects existing patterns, scripting that doesn't fight the engineer. Most identity tools don't have a CLI; the customers who would benefit most build their own.
The Oleria IAM Engineer Command-Line Interface brings identity querying and automation into the terminal — pipe results to jq, script reviews, and run investigations without breaking your shell workflow.
Query, investigate, modify, export. All major operations exposed.
JSON, CSV, plain-text — suitable for piping to jq, awk, downstream tools.
Reuse the customer's existing identity (via SSO callback, environment-variable token, or system keychain). No separate password.
All operations work in non-interactive mode. Suitable for shell scripts, Makefiles, CI pipelines.
IAM engineer flow continuity — Higher (no terminal-to-GUI context switches)
Hand-built API wrapper code — Replaceable
CLI-driven automation — Common
Time per ad-hoc identity investigation — Materially reduced for terminal-native engineers
Identity work shouldn't require a browser tab when your team lives in the shell. The Oleria CLI puts every identity query, investigation, and automation a keystroke away — pipe-friendly, scriptable, and built for the IAM engineer's daily workflow.
Mirrors the API. Query, list, get, modify, revoke, certify, export. All major operations. Subcommand structure mirrors the resource model: oleria identity get, oleria access-graph query, oleria review list. The CLI is the API in shell-friendly form.
Default is human-readable text. JSON for piping to jq or downstream tooling. CSV for opening in Excel or piping to data processing. Format flag is consistent across commands. Easy to integrate the CLI into any data pipeline.
First run: SSO callback opens the browser, you authenticate, the credential is cached locally (system keychain or encrypted file). Subsequent commands use the cached credential until expiration. For non-interactive use (CI, scripts): environment-variable token; standard pattern.
Yes. Every command works in non-interactive mode (no prompts when not in a terminal). Exit codes follow conventions (0 success, non-zero failure with specific codes for common failure types). Output to stderr vs. stdout is split correctly. Fits naturally in shell scripts, Makefiles, and CI pipelines.
IAM engineers who live in the terminal. Detection engineers piping identity data into their analysis. Cloud engineers querying identity context as part of cloud work. Anyone whose primary work surface is the shell. The CLI's existence pulls these users into Oleria where the GUI alone wouldn't.
