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
It seems possible to avoid discovery altogether by specifying issuer instead of issuerBaseURL, and this is perfectly fine with symmetrical algorithms. However, it seems impossible to provide an asymmetrical algorithm and not specify issuerBaseURL.
Describe the ideal solution
I would like to pass the public key explicitly without doing discovery. So something like defining issuer, audience, and then public key in secret. The library jose seems to allow passing the public key already, but we never get here because node-oauth2-jwt-bearer will throw before that during validation.
Alternatives and current workarounds
Currently not possible.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I've came across this issue trying to migrate from express-jwt and having the same problem.
Is there any suggested workaround? Hoping to not have to introduce JWKS for this asymmetrical setup where I have the public key available to me which I hoped to pass into secret.
Otherwise faced with jose or a jsonwebtoken approach but not sure where to turn.
Checklist
Describe the problem you'd like to have solved
It seems possible to avoid discovery altogether by specifying
issuer
instead ofissuerBaseURL
, and this is perfectly fine with symmetrical algorithms. However, it seems impossible to provide an asymmetrical algorithm and not specifyissuerBaseURL
.Describe the ideal solution
I would like to pass the public key explicitly without doing discovery. So something like defining
issuer
,audience
, and then public key insecret
. The libraryjose
seems to allow passing the public key already, but we never get here becausenode-oauth2-jwt-bearer
will throw before that during validation.Alternatives and current workarounds
Currently not possible.
Additional context
No response
The text was updated successfully, but these errors were encountered: