stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

Finalize UI truthfulness and bootstrap hardening

Browse Source
This commit is contained in:
master
2026-04-16 16:23:54 +03:00
parent 4799aa2402
commit bc6b1c5959
145 changed files with 10503 additions and 9837 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/modules/cli/guides/commands/auth.md
View File

@@ -11,11 +11,17 @@ Acquire and cache an access token using the configured Authority credentials.
```bash
stella auth login
stella auth login --force
STELLAOPS_AUTHORITY_CLIENT_ID=stellaops-cli-automation \
STELLAOPS_AUTHORITY_CLIENT_SECRET=stellaops-local-cli-automation-secret \
stella auth login --json
```
Notes:
- `--force` ignores cached tokens and forces re-authentication.
- Credential sources are configuration-driven (profile/env). This command does not accept raw tokens on the command line.
- When no Authority client ID is configured, the CLI defaults to the seeded human client `stellaops-cli`.
- In a fresh interactive local/dev shell, `auth login` prompts for username/password and uses the current password-grant bootstrap path on that human client.
- For non-interactive automation, configure a confidential client such as the seeded local/dev `stellaops-cli-automation`.
### auth status / whoami / logout
@@ -82,4 +88,3 @@ Flags:
## Offline notes
- `auth login` and token mint/delegate require connectivity to Authority.
- `auth revoke verify`, `status`, `whoami`, and `logout` can operate using local cached state.