You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using zitadel/oidc to create an OpenID Provider.
I believe the library intends that the VerifyJWTAssertion function is called when client authentication is done with private_key_jwt.
However, this function currently only supports RS256 since the supportedSigAlgs argument is nil when executing the CheckSignature function.
Therefore I would like to sign with ES256, which is not possible.
Describe your ideal solution
Since the FAPI states that PS256 or ES256 is recommended, why not support PS256 or ES256 if it is not specified here as well?
Version
v3.22.1
Environment
Self-hosted
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Describe your problem
I am using zitadel/oidc to create an OpenID Provider.
I believe the library intends that the VerifyJWTAssertion function is called when client authentication is done with private_key_jwt.
However, this function currently only supports RS256 since the supportedSigAlgs argument is nil when executing the CheckSignature function.
Therefore I would like to sign with ES256, which is not possible.
Describe your ideal solution
Since the FAPI states that PS256 or ES256 is recommended, why not support PS256 or ES256 if it is not specified here as well?
Version
v3.22.1
Environment
Self-hosted
Additional Context
No response
The text was updated successfully, but these errors were encountered: