Repository navigation
whoami shows no user for a sign-in: the app does not publish who the user is #182
Description
Measured
After a browser sign-in with the published CLI (0.4.4, macOS), hodeishield whoami prints Profile, API, App, Credential, Issuer, Expires and Scopes, but no User line ("user": null with --json).
The CLI reads the user from the authorization server's userinfo_endpoint (auth/oauth.rs, userinfo) and leaves the line out when there is none. The published authorization-server metadata (/.well-known/oauth-authorization-server/api/auth) has no userinfo_endpoint and offers no openid, profile or email scope, so there is nothing to call. GET /v1/me (API document 2026-10-19) describes the credential, tenant and organisation, but not the user.
Acceptance criteria
- After a sign-in,
whoamishows the signed-in user (name and email) in the table and in--json(user), read fromGET /v1/me. - With an API key or a portfolio key there is no user line, as today.
- Names from the API are cleaned before they are printed; a test covers it.
- No new OAuth scope is requested for this.
Depends on
The API: GET /v1/me returning the user (id, name, email) for a sign-in token.
Activity
d0ubl3g commentedon Oct 15, 2026
The CLI side is in
dev(#189):whoamireads the signed-in user fromGET /v1/mewhen the API provides it, and ignores it for keys. Output does not change until the API returns the field. This issue stays open until a sign-in shows the user against the published API.d0ubl3g commentedon Oct 15, 2026
Reopened: version 0.5.0 reads the signed-in user from
GET /v1/meand shows it in theUserline and in--json(user), but the published API document (2026-10-19) does not returnuserin that response yet, sowhoamistill shows no user after a sign-in. This stays open until the API sends it.d0ubl3g commentedon Oct 18, 2026
Verified against the published API with version 0.5.0 on Linux, 2026-10-19:
whoamishowsUser <name> <<email>>in the table, andwhoami --jsoncarries the same value inuser, read fromGET /v1/me.commands/session.rs; the API-key and portfolio-key path (no user line) is covered by the same tests.Closing.