Learn how to make the most out of the Dropbox Community here 💙!
Forum Discussion
Solved
OAuth access token type
Currently during authentication retyrned URL contains token_type=bearer parameter while respective header must be Bearer (else 400 is returned). Is that possible to return correct case in token_type...
According to the documentation, we only support the "bearer" token type, so any of these should be fine.
Thank you, Greg, for response.
Even it this is intensionally and won't be changed in future, I would appreciate advices of the parameter usage:
- Implement own mapping from types returned in the URL to proper header values (need the ful list of supported types described in documentation with stress on the correct capitalizing)
- Use types from URL but capitalize it (now it's my curren implementation)
- Always use Bearer in the auth header and ignore the type from URL
Greg-DB
Dropbox Staff
Dropbox StaffAccording to the documentation, we only support the "bearer" token type, so any of these should be fine.
Hi Greg,
the api does not accept "bearer", it only accepts "Bearer".
the returned value in token_type is "bearer" and most oauth clients will use that value to compose the Authorization Header.
the result is that the Authorization being sent to subsequent requests has the Authorization header "Authorization: bearer xxxxx" instead of "Authorization: Bearer xxxxx".
it seems to me that, the token_type value returned should be "Bearer" instead of "bearer" if api only accepts that, or change the api to accept "bearer".
thoughts ?
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
