Blog post on the support of OpenID4VCI #682

IngridPuppet · 2025-12-03T15:31:56Z

An initial version, so as to collect further early feedback.

Partially addresses #666 and #668 (They are duplicate)
Closes #666 (Let this initial draft close one)

Regarding the video, we're waiting for blocking UI PRs to merged first.

Closes keycloak#666 Signed-off-by: Ingrid Kamga <[email protected]>

Signed-off-by: Awambeng Rodrick <[email protected]> Signed-off-by: Ingrid Kamga <[email protected]>

ahus1

Thank you for the blog post. See below for some comments.

At the end (or the beginning), do you want to have a call-to-action how people should provide feedback? Do you want to add a GitHub discussion, or the slack channel of the working group?

blog/2025/issue-credentials-over-openid4vci.adoc

Signed-off-by: Awambeng Rodrick <[email protected]>

Awambeng · 2025-12-04T17:03:18Z

Hi @ahus1, I’ve addressed the comments you left. Could you please take a look when you get a chance?

Signed-off-by: Alexander Schwartz <[email protected]>

ahus1 · 2025-12-04T17:57:37Z

@Awambeng - thank you for the changes. This now looks good. Some minor added links here - please merge that PR into your PR, and then it should be good from a technical writer's point of view.

ADORSYS-GIS#3

Please have someone from the working group review the content. Thanks!

Resolved

Awambeng · 2025-12-04T19:10:36Z

@ahus1 Thank you very much for the review and improvements. We haven’t received any feedback from the SIG members yet.

@tnorimat @VinodAnandan @mposolda @thomasdarimont Could you please help review this PR when you have a moment?

thomasdarimont

I added some comments regarding content.

Also I like the useful graphics!

Would it be possible to change Keycloak_Issuer in the graphics to
Issuer
?

E.g. similar to this:

blog/2025/issue-credentials-over-openid4vci.adoc

Awambeng · 2025-12-05T09:10:39Z

@thomasdarimont @VinodAnandan Thank you for your reviews. Unfortunately, I can’t re-request your reviews, but feel free to take a look as all your comments and suggestions have been addressed.

blog/2025/issue-credentials-over-openid4vci.adoc

VinodAnandan · 2025-12-05T09:41:58Z

@IngridPuppet @Awambeng @thomasdarimont Should we consider including the following in the Concrete Use-Cases section? I believe it highlights one of the strongest privacy and security advantages of digital credentials.

Selective disclosure for low-trust scenarios - For example, a user can present only the minimum necessary information (such as a photo and confirmation that they are above a certain age) to a bouncer or security guard, without revealing their full identity or personal details.

Awambeng · 2025-12-05T10:11:02Z

@IngridPuppet @Awambeng @thomasdarimont Should we consider including the following in the Concrete Use-Cases section? I believe it highlights one of the strongest privacy and security advantages of digital credentials.

Selective disclosure for low-trust scenarios - For example, a user can present only the minimum necessary information (such as a photo and confirmation that they are above a certain age) to a bouncer or security guard, without revealing their full identity or personal details.

@VinodAnandan I might be wrong, but I see this example as more tied to SD-JWT VCs. Instead, I updated the first example in the list to highlight the security aspect you mentioned. Hope that works!

@IngridPuppet @thomasdarimont WDYT?

IngridPuppet · 2025-12-05T10:13:18Z

@IngridPuppet @Awambeng @thomasdarimont Should we consider including the following in the Concrete Use-Cases section? I believe it highlights one of the strongest privacy and security advantages of digital credentials.

Selective disclosure for low-trust scenarios - For example, a user can present only the minimum necessary information (such as a photo and confirmation that they are above a certain age) to a bouncer or security guard, without revealing their full identity or personal details.

Yes, definitely. It is well-known that the general public is often reluctant to the feature until selective disclosure is mentioned.

mposolda

Thanks @Awambeng and @IngridPuppet for the nice blog and for applying most of my suggestions I've sent earlier by the email.

Added 2 additional comments inline. Could you please double-check?

mposolda · 2025-12-08T10:30:20Z

blog/2025/issue-credentials-over-openid4vci.adoc

+
+- Attribute `vc.format` defines the format of the credential whereas `vc.verifiable_credential_type` specifies the `vct` property's value.
+- All `vc.display` entries are intended to be used by a wallet to display intelligible descriptions.
+- Known bugs mandate configuring the credential signing algorithm via `vc.proof_signing_alg_values_supported`.


What exactly are these "Known bugs" ? Are these Keycloak bugs? If yes, then it might be good to rather fix it on Keycloak side or at least create the GH issue on Keycloak side and refer it from here with the link? Last week, I've created keycloak/keycloak#44699 , which is slightly related, but probably different than the issue you have in mind?

Or is it bug in the OID4VCI specification itself or some other party? In that case, it can be maybe good to describe the limitation in the specification somehow as part of this point.

Hi Marek. It's not an issue with the OID4VCI specification. We created issue keycloak/keycloak#44621 to address it. A PR is in queue.

@IngridPuppet Thanks for the clarification! So if I understand correctly, that PR keycloak/keycloak#44621 needs to be merged first before this blog is published and then this blog-post can be updated to align with it (including renaming the option and slightly rewriting this sentence to avoid using "Known bugs mandate ..." formulation :-)

Is it correct?

Yes, we are on par. The whole bullet mentioning "Known bugs..." is meant to be removed after ticket keycloak/keycloak#44621 is completed. We hope such updates on the blog post could be done with iterative PRs prior to considering publishing it.

blog/2025/issue-credentials-over-openid4vci.adoc

tnorimat

@IngridPuppet Hello, I added some review comments. Could you check them?

blog/2025/issue-credentials-over-openid4vci.adoc

Awambeng · 2025-12-18T07:57:54Z

@VinodAnandan @mposolda I’ve closed the other PR, and all the changes are now consolidated here as suggested.

mposolda · 2026-01-09T16:23:54Z

@IngridPuppet @Awambeng @VinodAnandan @tnorimat It seems to me that main question is whether we "base" this blog-post based on Keycloak 26.5.0 release or based on the last "nightly" build?

So far, it seems to me that it can be better if we "base" this blog-post based on the last Keycloak 26.5.0 release.

I see the main disadvantage of the nightly release is, that OID4VCI is still under development. Hence this blog-post will probably quickly become outdated. For example when we publish this blog-post today, but someone will try instructions from this blog-post in 3 weeks from now (with the nightly build from February 1 for example), he will see different behaviour than described in this blog-post and maybe instructions will not work for him at all.

So my vote is to make this based on the Keycloak 26.5.0 release, but add paragraph at the bottom of the blog-post, that OID4VCI is still under development and instructions and configuration options from the blog-post may change in the future Keycloak versions. WDYT?

If we go this path, I guess some small updates would be needed in the blog-post (AFAIK for example option "Credential Signing Algorithm" mentioned in the blog-post is not yet available in Keycloak 26.5.0 admin console. However it may not be needed to create client-scope with this option configured AFAIK as long as the created ES256 is set as realm active key).
In that case, it may be good to also update links to the Keycloak documentation to 26.5.0 docs instead of "nightly" docs.

WDYT?

Awambeng · 2026-01-12T07:49:42Z

@IngridPuppet @Awambeng @VinodAnandan @tnorimat It seems to me that main question is whether we "base" this blog-post based on Keycloak 26.5.0 release or based on the last "nightly" build?

So far, it seems to me that it can be better if we "base" this blog-post based on the last Keycloak 26.5.0 release.

I see the main disadvantage of the nightly release is, that OID4VCI is still under development. Hence this blog-post will probably quickly become outdated. For example when we publish this blog-post today, but someone will try instructions from this blog-post in 3 weeks from now (with the nightly build from February 1 for example), he will see different behaviour than described in this blog-post and maybe instructions will not work for him at all.

So my vote is to make this based on the Keycloak 26.5.0 release, but add paragraph at the bottom of the blog-post, that OID4VCI is still under development and instructions and configuration options from the blog-post may change in the future Keycloak versions. WDYT?

If we go this path, I guess some small updates would be needed in the blog-post (AFAIK for example option "Credential Signing Algorithm" mentioned in the blog-post is not yet available in Keycloak 26.5.0 admin console. However it may not be needed to create client-scope with this option configured AFAIK as long as the created ES256 is set as realm active key). In that case, it may be good to also update links to the Keycloak documentation to 26.5.0 docs instead of "nightly" docs.

WDYT?

Thanks @mposolda, I agree. Basing the blog post on Keycloak 26.5.0 is safer and avoids issues with fast-changing nightly behavior. Adding a short disclaimer about OID4VCI still being under development makes sense.

One concern I have is that for Keycloak 26.5.0 to be fully functional, an additional configuration is required (the Credential Signing Algorithm), and optionally the changes from this PR: keycloak/keycloak#44874. Without this, some fields are currently saved as empty strings, which leads to runtime issues.

It would also be good to address this issue: keycloak/keycloak#44699, as currently it requires explicitly setting the Credential Signing Key ID during client scope creation.

Do we have an idea when the next patch release is planned, and whether it would be possible to include these changes? That would help ensure we have a stable version to base the blog post on.

mposolda · 2026-01-12T10:57:42Z

@IngridPuppet @Awambeng @VinodAnandan @tnorimat It seems to me that main question is whether we "base" this blog-post based on Keycloak 26.5.0 release or based on the last "nightly" build?
So far, it seems to me that it can be better if we "base" this blog-post based on the last Keycloak 26.5.0 release.
I see the main disadvantage of the nightly release is, that OID4VCI is still under development. Hence this blog-post will probably quickly become outdated. For example when we publish this blog-post today, but someone will try instructions from this blog-post in 3 weeks from now (with the nightly build from February 1 for example), he will see different behaviour than described in this blog-post and maybe instructions will not work for him at all.
So my vote is to make this based on the Keycloak 26.5.0 release, but add paragraph at the bottom of the blog-post, that OID4VCI is still under development and instructions and configuration options from the blog-post may change in the future Keycloak versions. WDYT?
If we go this path, I guess some small updates would be needed in the blog-post (AFAIK for example option "Credential Signing Algorithm" mentioned in the blog-post is not yet available in Keycloak 26.5.0 admin console. However it may not be needed to create client-scope with this option configured AFAIK as long as the created ES256 is set as realm active key). In that case, it may be good to also update links to the Keycloak documentation to 26.5.0 docs instead of "nightly" docs.
WDYT?

Thanks @mposolda, I agree. Basing the blog post on Keycloak 26.5.0 is safer and avoids issues with fast-changing nightly behavior. Adding a short disclaimer about OID4VCI still being under development makes sense.

One concern I have is that for Keycloak 26.5.0 to be fully functional, an additional configuration is required (the Credential Signing Algorithm), and optionally the changes from this PR: keycloak/keycloak#44874. Without this, some fields are currently saved as empty strings, which leads to runtime issues.

It would also be good to address this issue: keycloak/keycloak#44699, as currently it requires explicitly setting the Credential Signing Key ID during client scope creation.

Do we have an idea when the next patch release is planned, and whether it would be possible to include these changes? That would help ensure we have a stable version to base the blog post on.

I am not sure about backporting those to patch release as those are related to experimental feature... If saving client scopes from admin console still has limitations in Keycloak 26.5.0, is it perhaps possible to fallback to admin REST API directly in this blog-post as it was before?

Awambeng · 2026-01-12T13:45:46Z

I am not sure about backporting those to patch release as those are related to experimental feature... If saving client scopes from admin console still has limitations in Keycloak 26.5.0, is it perhaps possible to fallback to admin REST API directly in this blog-post as it was before?

@mposolda I've updated the blog post as suggested. Could you please take a look?

mposolda

@Awambeng Nice, Thanks!

I've added some last minor comments regarding the "Publishing date" and feedback, but I hope we can merge this very soon. Leaving for tomorrow to eventually provide some last reviews (if someone still has some review points). Otherwise hope to merge on Friday.

mposolda · 2026-01-14T16:02:26Z

blog/2025/issue-credentials-over-openid4vci.adoc

@@ -0,0 +1,379 @@
+:title: Setting Up Keycloak as a Credential Issuer with OpenID4VCI
+:date: 2025-12-02


Is it possible to update this date for example to 2026-01-16 ? This means Friday this week. I hope we can merge this PR on Friday and hence the date would be accurate (this mechanism of date hardcoded in the PR file itself is not so ideal, but that is how it works in current Keycloak blog posts...).

mposolda · 2026-01-14T16:06:24Z

blog/2025/issue-credentials-over-openid4vci.adoc

+
+== Important Note on OpenID4VCI Development Status
+
+OpenID4VCI support in Keycloak is still under active development. The instructions and configuration options described in this blog post are based on *Keycloak 26.5.0* and may change in future Keycloak versions as the feature evolves.


Suggested change

OpenID4VCI support in Keycloak is still under active development. The instructions and configuration options described in this blog post are based on *Keycloak 26.5.0* and may change in future Keycloak versions as the feature evolves.

OpenID4VCI support in Keycloak is still under active development. The instructions and configuration options described in this blog post are based on *Keycloak 26.5.0* and may change in future Keycloak versions as the feature evolves. If you want to look at latest updates in the OID4VCI feature, then you can use latest https://www.keycloak.org/nightly/[Keycloak nightly release], however be aware that instructions in this blog may not work with that version.

Is it possible to add some small sentence about "nightly" build as we briefly discussed on today's meeting? For example something like I've suggested?

mposolda · 2026-01-14T16:11:18Z

blog/2025/issue-credentials-over-openid4vci.adoc

+We’d love to hear your thoughts on this guide! You can provide feedback or ask questions through:
+
+* Slack: Join the https://slack.cncf.io/[Cloud Native Computing Foundation (CNCF) Slack] and discuss with us in the channel https://cloud-native.slack.com/channels/keycloak-oauth-sig[#keycloak-oauth-sig].
+


Suggested change

* Github: Inspect and join recent https://github.com/keycloak/keycloak/discussions?discussions_q=is%3Aopen+oid4vci[OpenID4VCI related Github discussions]. Inspect https://github.com/keycloak/keycloak/issues?q=is%3Aissue%20state%3Aopen%20label%3Aarea%2Foid4vc[existing OpenID4VCI related Github issues] and feel free to comment/upvote some of them or create new issue if you have idea for the enhancement or if you found a bug.

Is it possible to add a note about feedback on Github? For example something like I've added above? WDYT?

mposolda · 2026-01-14T16:13:42Z

@Awambeng Could you please also rebase this PR on top of latest Keycloak-web main?

Signed-off-by: Awambeng Rodrick <[email protected]>

…in REST API with UI-based instructions Signed-off-by: Awambeng Rodrick <[email protected]>

… for enabling Verifiable Credentials Signed-off-by: Awambeng Rodrick <[email protected]>

…and removing signing key ID Signed-off-by: Awambeng Rodrick <[email protected]>

…ayground OID4VCI demo and improving phrasing Signed-off-by: Awambeng Rodrick <[email protected]>

Signed-off-by: Awambeng Rodrick <[email protected]>

… to use Admin REST API, and clarify OpenID4VCI development status Signed-off-by: Awambeng Rodrick <[email protected]>

Signed-off-by: Awambeng Rodrick <[email protected]>

Awambeng · 2026-01-15T08:08:26Z

@mposolda I’ve rebased on the latest main and addressed your comments as suggested. Could you please have another look?

mposolda

@Awambeng Thanks! Hope to merge tomorrow (if there is no one else wanting to review/comment).

thomasdarimont · 2026-01-15T08:46:18Z

I read throught he blogpost again! Looks very good now :)

Maybe a followup blogpost cloud also show how the generated SD-JWT VC credential looks like.
The current blog post shows how to obtain the credential, and how it eventually looks like in a wallet, but doesn't show the actual transport format SD-JWT VC, which is also probably new to many readers.

embesozzi · 2025-12-23T19:21:09Z

blog/2025/issue-credentials-over-openid4vci.adoc

+7. The **Wallet** requests the **Verifiable Credential** from the **Issuer Credential Endpoint** using the Access Token.
+8. The **Issuer** returns the **VC** to the Wallet.
+
+.Credential issuance via Authorization Code Flow


We can use a Mermaid sequence diagram instead of an image. it will be easier to maintain.
Here is the code for authorization-code-flow.png.

sequenceDiagram autonumber participant Wallet participant User participant Issuer as Issuer <br/><Keycloak> Wallet->>Issuer: Authorization Request (request credentials) Issuer->>User: Authenticate user and request consent User->>Issuer: Provide credentials and grant consent Issuer-->>Wallet: Return Authorization Code Wallet->>Issuer: Exchange Authorization Code for Access Token (Token Endpoint) Issuer-->>Wallet: Return Access Token Wallet->>Issuer: Request Verifiable Credential (VC Endpoint) using Access Token Issuer-->>Wallet: Return Verifiable Credential (VC)

Loading

Thanks @embesozzi, that makes sense. Using a Mermaid sequence diagram would definitely be easier to maintain.
The only concern is that our current setup does not seem to support Mermaid, so it would not render properly in the blog post.
@mposolda, what do you think? Should we look into adding Mermaid support, or keep the image for now?

Mermaid is great, but if it is not properly rendered on the web-page and on the blog, then it is not so good option IMO.

Also regarding blog-post, I do not think that we care about maintenance as when blog-post is published, it is usually not later updated. So image is fine for this blog-post IMO.

However we care about maintenance for the Keycloak documentation. For that one, we use https://draw.io for the diagrams. This is not so nice and easy like mermaid, but it works well in Keycloak documentation. See for example token exchange diagram or some other diagrams in the HA guide https://www.keycloak.org/guides#high-availability ).
It seems next step might be to add those nice pictures to the Keycloak documentation and hence possibly rewrite them to use draw.io ? However that is a follow-up not directly related to this blog-post though, but rather to Keycloak documentation...

embesozzi · 2025-12-23T19:26:15Z

blog/2025/issue-credentials-over-openid4vci.adoc

+4. The **Wallet** requests the **Verifiable Credential** from the **Issuer Credential Endpoint** using the Access Token.
+5. The **Issuer** returns the **VC** to the Wallet.
+
+.Credential issuance via Pre-Authorized Code Flow


Same here. Below is the code for pre-authorization-code-flow.png.

sequenceDiagram autonumber participant Wallet participant Issuer as Issuer <br><Keycloak> Issuer-->>Wallet: Send Pre-Authorized Code (QR code or link) Wallet->>Issuer: Exchange Pre-Authorized Code for Access Token (Token Endpoint) Issuer-->>Wallet: Return Access Token Wallet->>Issuer: Request Verifiable Credential (Credential Endpoint) using Access Token Issuer-->>Wallet: Return Verifiable Credential (VC)

Loading

mposolda · 2026-01-15T17:58:44Z

I read throught he blogpost again! Looks very good now :)

Maybe a followup blogpost cloud also show how the generated SD-JWT VC credential looks like. The current blog post shows how to obtain the credential, and how it eventually looks like in a wallet, but doesn't show the actual transport format SD-JWT VC, which is also probably new to many readers.

+1 . This can be also nice to better document in the Keycloak documentation. I am not sure how far to go as we probably do not want to duplicate whole sd-jwt format details in the Keycloak docs, but maybe something readable (with nice pictures and easy examples to follow) like for example in the curity docs might be great

embesozzi · 2026-01-16T11:40:25Z

Just a minor observation: it would be good to show all URLs in the code examples and images over https instead of http. It’s just a personal preference, but I don’t like showing examples or documentation over plain text.

IngridPuppet force-pushed the openid4vci branch from 613b89a to b9d7bc8 Compare December 3, 2025 15:36

IngridPuppet and others added 2 commits December 3, 2025 16:44

Draft blog post about OpenID4VCI in Keycloak

43c47e8

Closes keycloak#666 Signed-off-by: Ingrid Kamga <[email protected]>

Improve blog post (@Awambeng)

fc93520

Signed-off-by: Awambeng Rodrick <[email protected]> Signed-off-by: Ingrid Kamga <[email protected]>

IngridPuppet force-pushed the openid4vci branch from b9d7bc8 to fc93520 Compare December 3, 2025 15:44

ahus1 previously requested changes Dec 4, 2025

View reviewed changes

Address @ahus1 review comments

a500df1

Signed-off-by: Awambeng Rodrick <[email protected]>

IngridPuppet requested a review from ahus1 December 4, 2025 17:05

Review

e574d56

Signed-off-by: Alexander Schwartz <[email protected]>

ahus1 mentioned this pull request Dec 4, 2025

Review to add some more links ADORSYS-GIS/keycloak-web#3

Merged

ahus1 removed their request for review December 4, 2025 18:08

thomasdarimont reviewed Dec 4, 2025

View reviewed changes

VinodAnandan reviewed Dec 5, 2025

View reviewed changes

blog/2025/issue-credentials-over-openid4vci.adoc Outdated Show resolved Hide resolved

thomasdarimont reviewed Dec 5, 2025

View reviewed changes

blog/2025/issue-credentials-over-openid4vci.adoc Outdated Show resolved Hide resolved

thomasdarimont reviewed Dec 5, 2025

View reviewed changes

blog/2025/issue-credentials-over-openid4vci.adoc Outdated Show resolved Hide resolved

thomasdarimont reviewed Dec 5, 2025

View reviewed changes

blog/2025/issue-credentials-over-openid4vci.adoc Outdated Show resolved Hide resolved

thomasdarimont reviewed Dec 5, 2025

View reviewed changes

blog/2025/issue-credentials-over-openid4vci.adoc Outdated Show resolved Hide resolved

IngridPuppet requested a review from VinodAnandan December 5, 2025 09:32

mposolda requested review from mposolda and removed request for VinodAnandan December 6, 2025 08:40

mposolda reviewed Dec 8, 2025

View reviewed changes

mposolda mentioned this pull request Dec 8, 2025

OID4VCI documentation polishing keycloak/keycloak#44738

Open

tnorimat reviewed Dec 9, 2025

View reviewed changes

mposolda reviewed Jan 14, 2026

View reviewed changes

mposolda changed the title ~~Draft blog post on the support of OpenID4VCI~~ Blog post on the support of OpenID4VCI Jan 14, 2026

Awambeng added 13 commits January 15, 2026 08:42

Address @thomasdarimont review comments

313c959

Signed-off-by: Awambeng Rodrick <[email protected]>

Apply suggestions from @VinodAnandan

e7ac07e

Signed-off-by: Awambeng Rodrick <[email protected]>

Address further comments from @thomasdarimont and @VinodAnandan

d64d645

Signed-off-by: Awambeng Rodrick <[email protected]>

Address @tnorimat review comments

3b58fee

Signed-off-by: Awambeng Rodrick <[email protected]>

Update OpenID4VCI guide to include OpenID4VP and enhance clarity

52cf249

Signed-off-by: Awambeng Rodrick <[email protected]>

chore: improve client scope and mapper configuration by replacing Adm…

29425dd

…in REST API with UI-based instructions Signed-off-by: Awambeng Rodrick <[email protected]>

docs: update OpenID4VCI configuration instructions and add screenshot…

7d5b499

… for enabling Verifiable Credentials Signed-off-by: Awambeng Rodrick <[email protected]>

docs: update client scope configuration by adjusting column settings …

3098ca6

…and removing signing key ID Signed-off-by: Awambeng Rodrick <[email protected]>

docs: enhance OpenID4VCI blog post by adding reference to Keycloak Pl…

f168550

…ayground OID4VCI demo and improving phrasing Signed-off-by: Awambeng Rodrick <[email protected]>

docs: correct terminology in credential signing section for clarity

08aee96

Signed-off-by: Awambeng Rodrick <[email protected]>

docs: update claim terminology in mapper configuration for clarity

7381fea

Signed-off-by: Awambeng Rodrick <[email protected]>

docs: update notes on Keycloak's OpenID4VCI support status for clarity

8439aaf

Signed-off-by: Awambeng Rodrick <[email protected]>

docs: update Keycloak version reference, adjust client scope creation…

67b2c75

… to use Admin REST API, and clarify OpenID4VCI development status Signed-off-by: Awambeng Rodrick <[email protected]>

Awambeng force-pushed the openid4vci branch from 1aa9a58 to 67b2c75 Compare January 15, 2026 07:42

Address review comments from @mposolda

9ff5885

Signed-off-by: Awambeng Rodrick <[email protected]>

mposolda approved these changes Jan 15, 2026

View reviewed changes

embesozzi reviewed Jan 15, 2026

View reviewed changes

mposolda merged commit c39880c into keycloak:main Jan 16, 2026
1 of 3 checks passed

		@@ -0,0 +1,379 @@
		:title: Setting Up Keycloak as a Credential Issuer with OpenID4VCI
		:date: 2025-12-02


		== Important Note on OpenID4VCI Development Status

		OpenID4VCI support in Keycloak is still under active development. The instructions and configuration options described in this blog post are based on Keycloak 26.5.0 and may change in future Keycloak versions as the feature evolves.

		We’d love to hear your thoughts on this guide! You can provide feedback or ask questions through:

		* Slack: Join the https://slack.cncf.io/[Cloud Native Computing Foundation (CNCF) Slack] and discuss with us in the channel https://cloud-native.slack.com/channels/keycloak-oauth-sig[#keycloak-oauth-sig].

Blog post on the support of OpenID4VCI #682

Blog post on the support of OpenID4VCI #682

Uh oh!

Conversation

IngridPuppet commented Dec 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ahus1 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Awambeng commented Dec 4, 2025

Uh oh!

ahus1 commented Dec 4, 2025

Uh oh!

Awambeng commented Dec 4, 2025

Uh oh!

thomasdarimont left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Awambeng commented Dec 5, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

VinodAnandan commented Dec 5, 2025

Uh oh!

Awambeng commented Dec 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

IngridPuppet commented Dec 5, 2025

Uh oh!

mposolda left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

tnorimat left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Awambeng commented Dec 18, 2025

Uh oh!

mposolda commented Jan 9, 2026

Uh oh!

Awambeng commented Jan 12, 2026

Uh oh!

mposolda commented Jan 12, 2026

Uh oh!

Awambeng commented Jan 12, 2026

Uh oh!

mposolda left a comment

Choose a reason for hiding this comment

IngridPuppet commented Dec 3, 2025 •

edited

Loading

Awambeng commented Dec 5, 2025 •

edited

Loading