feat: fix auth login validation and add auth whoami command#2
Merged
feat: fix auth login validation and add auth whoami command#2
Conversation
- auth login now validates against /api/v1/auth/me (works with API keys) instead of /platform/me (JWT-only, always failed for CLI users) - Shows org name, key name, and plan tier on successful login - New auth whoami command displays full identity, plan, usage, and rate limits Made-with: Cursor
Tries /api/v1/auth/me first (rich identity for API keys), falls back to /api/v1/dashboard/overview for dev tokens and JWTs. Made-with: Cursor
Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
auth login— validates againstGET /api/v1/auth/me(API-key-compatible) instead of/platform/me(JWT-only, always failed)auth whoamicommand — displays full API key identity, org, plan tier, entitlements with usage, and live rate-limit quotaDependencies
Requires mono#174 to be deployed first — the
/api/v1/auth/meendpoint must exist on the API before this CLI version is released.Test plan
devhelm auth login --token dh_live_...succeeds and shows org/key/plan infodevhelm auth whoamidisplays identity, plan, usage, and rate limitsdevhelm auth whoami --output jsonreturns full JSON responsedevhelm auth loginwith invalid token fails with proper error messageMade with Cursor