Repository navigation
Conversation
ikawalec
force-pushed
the
feat/cimd-example-documents
branch
from
September 29, 2026 14:20
0f4e76b to
ec97de5
Compare
This branch has not been deployed
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.
Adds three CIMD documents under
data/cimd/, served by the repo's GitHub Pages asapplication/json. Eachclient_idis the URL it is served from.public.json: public client (none, PKCE)private-key-jwt.json:private_key_jwt, keys viajwks_uri(data/rsa/public.json)private-key-jwt-inline-jwks.json:private_key_jwt, keys inline injwksThey reuse the existing test keys and the default callback
http://localhost:9876/callback, so they are for testing only. The README gets a short CIMD example; its issuer is a placeholder until a demo workspace with CIMD enabled exists.Each document declares
scope, since an authorization server may otherwise register the client with no scopes (RFC 7591 §2).Tested against SecureAuth (preprod) with the documents served from a tunnel: all three complete authorization code + PKCE and return access, ID and refresh tokens. The workspace must allow the
none/private_key_jwtclient authentication methods.