feat(console): private_key_jwt client UI (asymmetric, no secret)#25
Merged
Conversation
… + manifest hint Bumps server ^1.15 (client summary now reports the auth method). The OAuth-client panel renders a "private_key_jwt · asymmetric" badge, explains there is no shared secret (and whether a JWKS is registered), and hides the Rotate-secret button + secret-expiry line for such clients. The onboarding manifest field now documents auth.token_endpoint_auth_method = "private_key_jwt" + auth.jwks. SPA lint/build + 20 tests green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Server ^1.15 bump + Applications UI shows private_key_jwt clients as asymmetric (badge, no secret, JWKS state) and hides the secret-rotation controls; manifest field documents the private_key_jwt auth block.