-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECC Keys in JWKS Response cause Error #1
Comments
Hey Tim, Thanks for opening the issue. Is there any chance you could provide a sample keyset (json or url) to help me look at the issue? |
I do have to redact the actual key material for various reasons so sadly this won't enable you to test the verification itself. The JWKS Data is generated by Keycloak. |
That's perfect Tim. Much appreciated. |
Hey Tim, an updated version of jwks_client should be available in crate.io (0.1.8). If you could test and let me know if that fixes the error for you that would be greatly appreciated. Thanks again for your help. |
Thanks, I won't be able to test the code until early January since we are closed over christmas but I appreciate the quick fix! |
Thank. I'm make the issue as closed, but feel free to re-open should there be a problem. Have a great holiday! |
Hi, just a closing remark; I was able to test the patch and it works like a charm! Thank you very much! |
Thank you for helping me improve jwks-client! |
Currently if a JWKS Set contains both an RSA and a ECC key, jwks-client produces an error due to the missing
e
andn
fields in the ECC key.Using the
#[serde(default)]
tag in both fields solves the issue; as the library doesn't verify P256 keys, those will still fail but R256 keys continue to function, so it doesn't matter that the P256 key isn't a valid RSA key.The text was updated successfully, but these errors were encountered: