Skip to content

"invalid algorithm specified" error when using a valid algorithm but a missing or invalid auth_jwt_key #150

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
DevJake opened this issue Mar 12, 2025 · 0 comments

Comments

@DevJake
Copy link

DevJake commented Mar 12, 2025

As per the title, if you use a valid algorithm - such as ES256 - but the auth_jwt_key value is missing or invalid, then you are presented with the error "invalid algorithm specified". Whilst the fix is clear, the error message itself is not intuitive and is misleading. I ended up digging through some issues and PRs just to confirm that ES256 is actually supported (it isn't listed in the README, just a heads up!).

If possible, some logic should be added to distinguish between an invalid algorithm and an invalid public key, so future users aren't equally stumped.

Many thanks!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant