Replies: 1 comment 2 replies
-
|
Hello @edmaputra , I'm not sure which Key Provider you've implemented and how, but I assume that you've extended The issue you've reported might be occurred due to the following code. I'm not sure it works well but how about overriding this KeyUse keyUse = KeyUse.valueOf(model.get(Attributes.KEY_USE, KeyUse.SIG.name()).toUpperCase());
key.setUse(keyUse == null ? KeyUse.SIG : keyUse); |
Beta Was this translation helpful? Give feedback.
-
|
Hi @tnorimat Yes, I already use the Components you've mention before. I also override the I have found the cause. Invoked by this method to publish the JWKS So whatever the KeyUse I set, it will always publish as "sig" value. My current solution now is implementing a new custom REST API to publish the key. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @edmaputra , Yes, as you mentioned, the current keycloak does not consider EC key provider for key encryption. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have implemented a custom SPI for Key Provider to create a Key with EC, combine with nimbus-jose-jwt library so I can create a key with ECDH-ES+A128KW algorithm.
The key is generated successfully, but when I want to publish it in oidc jwks uri, the “use” keeps on “sig” value, even I set it to the “enc” in the configuration. I also try to force the “use” value to “enc” in the code but it still happening. Can someone explain why and what should I do ?
Beta Was this translation helpful? Give feedback.
All reactions