-
Notifications
You must be signed in to change notification settings - Fork 450
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
Problem different token types #180
Comments
Does it create error/exception? |
I have a client oauth2, It's connected with server that use "refresh_token":"Yjg4MjAyZmYzMTBkNTI4ZWVlYzkwYTczMTFhMjZjNTc3YTVjMjYxZjcyMWZhNDE2NWE2OGM4ZWUyZjQzNjAxYQ" My client use the token type of request for send the response for example $header = 'Authorization ' . sprintf("%s %s", getTokenType(), getTokenType() return the token type of response this is "bearer" but in Sorry for me English, I don't know more, I hope you understand me 2013/9/29 Alan Gabriel Bem notifications@github.com
|
@alanbem RFC 6750 section 4 in example shown value "Bearer" to "token_type" |
Ok the token_type as Bearer is correct, this isn't the problen, I have I think this is odd, I hope you understand me now, otherwise, this is not Thanks for you time. 2013/10/1 Vladislav Vlastovskiy notifications@github.com
|
Ok Excuse me @vlastv I thought you did not understand, my English is awful. 2013/10/1 Vladislav Vlastovskiy notifications@github.com
|
@jjbier I myself do not speak very much English, my native language is Russian :) Sorry for offtopic |
@jjbier everything was clear, thank you. Please, don't worry about your english it's fine. I will look into this problem later this week. |
So |
A workaround is to override the default token_type (which is bearer in lowercase' to Bearer (with an uppercase).
|
in response send
OAuth2::TOKEN_TYPE_BEARER = 'bearer'
in request check
OAuth2::TOKEN_BEARER_HEADER_NAME = 'Bearer';
suggesting
OAuth2::TOKEN_TYPE_BEARER = 'Bearer'
OAuth2::TOKEN_BEARER_HEADER_NAME = 'Bearer';
The text was updated successfully, but these errors were encountered: