-
Notifications
You must be signed in to change notification settings - Fork 16
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
Token changes? #8
Comments
DEBUG:revolut.session:TokenProvider request data: { |
I think Revolut changed the authorization method AGAIN. They now require X.509 certificates, which is not implemented but will be as soon as we need it :/ |
I thought the X.509 certificate was just for the first steps. Their documentation still talks about JWT for token exchange. Without the documentation update it's hard to know what to program differently!? |
Well, unfortunately they don't mention upcoming changes, nor version the API. |
Having trouble at step 12 and wonder if anything has changed recently. revolut_getjwt no longer seems to need the decode on the return, otherwise believe I have a valid jwt - generate new auth_code and request token but always get 400 status to the post for the token:
unauthorized_client: Failed to authorise client
Any help appreciated.
The text was updated successfully, but these errors were encountered: