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
The README indicates that if the token_payload is left unset, then it:
Defaults to a randomly generated token in a hash: { token: "RANDOM-TOKEN" }
However, that is not this library's current behavior.
The following is what is actually generated if you fail to set a token_payload:
{
"token": "#<Method: SecureRandom.hex>"
}
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:
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: