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 is a pretty common expectation that JWT's can be passed using the Bearer token approach. It is also recommended and the main source of info for JWT:
It is a common compliant our customers give us that they need to use Token instead of Bearer when using our API. They need to write more code to support it etc...
Would you accept pull requests to all both to be specified?
The text was updated successfully, but these errors were encountered:
You can accomplish this (at least, you can switch to "Bearer" instead of the default "Token") by using the :token-name option when setting up the back end.
It is a pretty common expectation that JWT's can be passed using the Bearer token approach. It is also recommended and the main source of info for JWT:
https://jwt.io
It is a common compliant our customers give us that they need to use
Token
instead ofBearer
when using our API. They need to write more code to support it etc...Would you accept pull requests to all both to be specified?
The text was updated successfully, but these errors were encountered: