We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems that after the change to jose-jwt in 465170c, we don't require a minimum of 32 characters for jwt-secret anymore.
jose-jwt
jwt-secret
The question is: Should we keep it like that or re-implement that limit ourselves? If we re-implement it, we can surely do #1840 (comment).
I tend to say the limit is useful and we should implement it again with a proper error message.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It seems that after the change to
jose-jwt
in 465170c, we don't require a minimum of 32 characters forjwt-secret
anymore.The question is: Should we keep it like that or re-implement that limit ourselves? If we re-implement it, we can surely do #1840 (comment).
I tend to say the limit is useful and we should implement it again with a proper error message.
The text was updated successfully, but these errors were encountered: