Skip to content

Conversation

@vharsh
Copy link
Contributor

@vharsh vharsh commented Feb 11, 2025

No description provided.

Copy link
Collaborator

@Varaniya201 Varaniya201 Apr 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Goal needs to be precise. Goal of this document is "Providing guidance to developer/user to integrate key cloak as an authentication service for VC issuance"
  2. Not required for non-goals
  3. Give an overview on what this document about

2. Create a "client scope" in Keycloak with the same scope name as the one configured in Certify Well Known
- set the "Protocol" to be `openid-connect`
- set "Include In Token Scope" to `true`
- Create mappers with the "token claim name" of `c_nonce_expires_in`, `aud`, `client_id`, `c_nonce` with the "Add to access token" set to `true`
Copy link
Contributor Author

@vharsh vharsh Apr 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Create mappers with the "token claim name" of `c_nonce_expires_in`, `aud`, `client_id`, `c_nonce` with the "Add to access token" set to `true`
- Create mappers with the "token claim name" of `aud` & `client_id` with the relevant details and set "Add to access token" to `true`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants