-
Notifications
You must be signed in to change notification settings - Fork 8
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
Question: what if token_type
is not always available
#37
Comments
Ugh, I just love how hard it seems to be for authorization servers to properly implement the OAuth2 standard 😅 The OAuth2 spec requires the token response to have this field, so this is technically a bug on LinkedIn's side. Still, I'm aware that there's a lot of implementations out there that don't follow the spec and I'll try to come up with a way to account for these discrepancies that doesn't require everyone to reinvent the wheel in the process. |
Tbh I haven't managed to auth with an OAuth based service yet that didn't use a |
token_type
is not always availabletoken_type
is not always available
Let the title represent it's LinkedIn's bug not the library's and we're questioning the problem to achieve a solution. |
Edit: Nevermind. We're getting a |
E.g. LinkedIn OAuth doesn't send the
token_type
in the response.https://learn.microsoft.com/en-us/linkedin/shared/authentication/authorization-code-flow?tabs=HTTPS1#response
Thus the getToken flow is erroring out.
https://github.com/cmd-johnson/deno-oauth2-client/blob/master/src/grant_base.ts#L99-L104
The text was updated successfully, but these errors were encountered: