-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
Help implementing new JWT token validation feature to the lbrary #71
Comments
I am trying to implement this functionality. I was able to write the entire code but the public key that is generated in not validating the signature using jwt.io. Can some one take a look at this code and point me what was the mistake. I feel that I have to add some headers to the pem key The final Pem key differs slightly by a bit. I guess I am missing something. Here is the difference in the keys that I see. There is an extra
The Code that I implemented. I guess OID is the issue, I think I have to get the ASN.1 for pcks(1) and update the OID with this value, I am not sure how I can get this. http://oid-info.com/get/1.2.840.113549.1.1.1
Reference: https://www.zash.se/jwk2pem.lua.html |
I've started to include this and use it for OIDC id_token validation as well in this branch: https://github.com/pingidentity/lua-resty-openidc/tree/support-rsa-kty-jwks |
Please take a look at this discussion, this might help |
Can someone add this functionality to this library. This will make this library to work for tokens which don't have x5c entry #34 . Function to convert public key to pem.
The text was updated successfully, but these errors were encountered: