Yacine BOUHALA authored Feb 22, 2023 and Romain Bignon committed Mar 04, 2023

sometimes, when we try to connect several times to our swile account
with wrong creds, we get a 401 error due to these wrong
creds generating an invalid token and the error message:
"Try again later. Your computer or network may be sending automated queries.
 To protect our users, we can’t process your request right now." or
"RECAPTCHA_INVALID_TOKEN"

droly authored May 16, 2022 and ntome committed May 23, 2022

The previous wrongpass message returned was:

"The provided authorization grant is invalid, expired,
revoked, does not match the redirection URI used in
the authorization request, or was issued to another client."

Which was not really relevant of the situation.

droly authored May 16, 2022 and ntome committed May 23, 2022

They changed the version from v2 to v3.
This is now an enterprise captcha.

I've also updated the headers sent.

Christophe François authored Dec 17, 2020 and hydrargyrum committed Dec 26, 2020

The status code for wrongpass is now 400 instead of 401. It's then
handled the same way as before.

ntome authored Jun 23, 2020 and hydrargyrum committed Aug 07, 2020

On first login, we have to solve a CAPTCHA to login, and then swile gives an
access_token and a refresh_token.
But unlike previous code, on subsequent logins, we can reuse the same
access_token, rather than solving the CAPTCHA again.
And when the access_token expires, we can simply use the refresh_token to get
a fresh access_token, rather than solving another CAPTCHA.

By using OAuth2Mixin, we leverage its token management.

Thibault Douge authored Apr 15, 2020 and hydrargyrum committed May 07, 2020

keep only the transaction of swile card

Closes: 18595@zendesk