-
Notifications
You must be signed in to change notification settings - Fork 45
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
Default token_payload doesn't return a random hex value #32
Comments
I can confirm this, I started with an empty config and noticed this as well when testing. |
I pushed up a fix for this issue: #56 |
Thank you, @ransombriggs! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The README indicates that if the
token_payload
is left unset, then it:However, that is not this library's current behavior.
The following is what is actually generated if you fail to set a
token_payload
:The token payload's default value does not appear to be getting called (the
hex
method reference is simply being converted to a string) and no random hash is generated:doorkeeper-jwt/lib/doorkeeper/jwt/config.rb
Lines 112 to 115 in 25223d6
The text was updated successfully, but these errors were encountered: