Skip to content
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

Open
MrSurf67 opened this issue Oct 11, 2022 · 4 comments
Open

Token changes? #8

MrSurf67 opened this issue Oct 11, 2022 · 4 comments

Comments

@MrSurf67
Copy link

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.

@MrSurf67
Copy link
Author

DEBUG:revolut.session:TokenProvider request data: {
"client_assertion": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJ3d3cudGVrZXZlci5jb20iLCJzdWIiOiJvYV9wcm9kX3NxVk1MR0JqLWZ3NXF1NEtpTU5HU3IzcFNtTldMV2IxeHI5QVJVcXpRZ0UiLCJhdWQiOiJodHRwczovL3Jldm9sdXQuY29tIn0.DvCJF8Z5vpWR4rTRmd4NBWnYN3NJhEW8LbOQ7dz13S3wZl9StNL-NPm_LfFN5YuWk8aO57tqra5FrxRJYwqM-Le0OmIFcXdGdCzC-dZkkzYBsuisEc8fGgZf4BKrhFQSeg2DQrzwTHfprHPxHHQTO-_aEom6FEpPlPdfSJGEj-Y",
"client_assertion_type": "urn:ietf:params:oauth:client-assertion-type:jwt-bearer",
"client_id": "jU61WxPv2Q1g1vKbzItJjbw7uv1g6aQg7C0yeq74SVE",
"code": "oa_prod_sqVMLGBj-fw5qu4KiMNGSr3pSmNWLWb1xr9ARUqzQgE",
"grant_type": "authorization_code"
}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): b2b.revolut.com:443
DEBUG:urllib3.connectionpool:https://b2b.revolut.com:443 "POST /api/1.0/auth/token HTTP/1.1" 400 None
DEBUG:revolut.session:TokenProvider result: {
"error": "unauthorized_client",
"error_description": "Failed to authorise client"
}

@emesik
Copy link
Member

emesik commented Oct 11, 2022

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 :/
Of course, PRs are always welcome if you chose to go ahead :)

@MrSurf67
Copy link
Author

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!?

@emesik
Copy link
Member

emesik commented Oct 11, 2022

Well, unfortunately they don't mention upcoming changes, nor version the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants