-
Notifications
You must be signed in to change notification settings - Fork 38
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
Version 1.4.3 crashes when fetching an access token #31
Comments
ollien
changed the title
Version 1.4.3 crashes when fetching an authorization token
Version 1.4.3 crashes when fetching an access token
Mar 28, 2024
Hm, on a whim I tried a fresh project with a more modern version of OTP (the above was using 21, my test project used 26), and this didn't seem to be a problem. I'll have to dig into this more, maybe this is just a non-issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There was a silent change in
jsx
version 3.0.0 which always addsreturn_maps
to the decode options, unlessreturn_maps
is explicitly specified (see: talentdeficit/jsx@fab436e#diff-442484fd845d07345ff2c60c11cb7f83288e6f11299be9b536594b66d3b09d85L75). The README of jsx does seem to confirm this is the default behavior. As a result, most requests for authorization tokens fail with the following, sinceoauth2c
still expects aproplist
for access token information.Version 1.4.2 still works fine, as this uses a 2.x release of
jsx
(or more accurately, the version ofrestclient
that 1.4.2 depends on uses a 2.x release).For the sake of providing some reproducing code, here's a lightly edited version of the code I used to reproduce this (though I would be surprised if it weren't reproducible with most flows),
I think that this patch would solve the issue, or at the very least put you closer to solving the issue #29
The text was updated successfully, but these errors were encountered: