- Jan 09, 2021
-
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
"No captcha" was the nickname of RecaptchaV2 service, but it's confusing and less precise. Rename and keep compatibility.
-
Authentication seems to have changed (#453), and in fact a few changes are needed to make it work again: * A new js page is now the target of the initial redirection chain, * This page gives us a new parameter ('goto') which is needed by the authenticate call * and old cookies need to be cleared before the authenticate call (otherwise an error is thrown)
-
-
In Value.check_valid method, regexp in validation error message is not consistent with actual matching test: it uses re.match and adds ending anchor. We can "normalize" regexp in objet initialization to be consistent.
-
-
-
A logger signaled that additionnal transactions where no longer loaded, compared to the minimal list shown when reaching OperationsPage the first time. Now get_form has been updated.
-
Sometimes, on creditfoncier, the wrongpass message is raised as a websiteUnavailable error.
-
Only for "professionnels" connections (current BProBrowser). It is the first part of the rework, other changes will come next. What is addressed so far: - login without sca, accounts, history, profile By the way, it also has the benefit of removing dead code: the variable `accounts_and_loans_url` doesn't seem to be used TODO: - implement the SCA - check if there are changes for wealth and bill with appropriate connections, and do the changes if needed - add new account types, etc...
-
The pro website has changed, and an url '.*voscomptes/identification/identification.ea.*' that was once handled as a temporary unvailability page is now an expected page of the login process. I don't know if this url has to be treated the same way or differently for the par website, so I decided to override the parent attribute in the subclass BProBrowser. We can also notice the following requests don't work because the pro website has changed (a wrong request will typically lead to a deconnection, for ex. the next_request auth_page() fails this way), but not for all connections (strange), meaning for some connections, the current requests work fine. So far I have noticed the current code still works for connections from users who have already validated the SCA (but I might have missed something else).
-
-
Allows to match the origin account by iban instead of by id.
-
-
-
The portfolio page takes more than 30s to load.
-
The name of a query parameter has changed, so the redirection URL was not recognized.
-
Some invests were missing because we only fetched the first `<div>` table. This works well with aviva but for the abstract module "afer" we must filter the `<tr>` from the "Répartition" table by counting their `<td>`. Also handled another xpath for opening_date.
-
-
-
Error 500 when searching detail of a 'Compte à terme', as on the website. Now raises a BrowserUnavailable.
-
We have a lot of transactions without label (ex: "referenceText" : "N26 Cashback")
-
-
hydrargyrum authored
-
-
The month selection in the history URL has changed from an index to a range of dates with a stupid format.
-
For some connections (approx. 3% total), life insurances link are broken on boursorama's website. This leads to unhandled 404 error which affects adding new connection and synchronizing existing ones. This commit provides a quick fix by catching 404 error in 'iter_accounts' for life insurance accounts and skipping them in that case.
-
-
-
-
When requesting to send the otp code to the user, the server can sometimes reply with a "authentsimple", that means that an otp is not needed anymore and will can just continue directly.
-
-
Example of raised message: "Nous ne pouvons pas réaliser cette opération en ligne. Merci de contacter votre conseiller."
-
-
-
- Jan 03, 2021
-
-
hydrargyrum authored
-
hydrargyrum authored
Also, show id of the broken parcel, so it's easy to untrack it.
-
hydrargyrum authored
-
- Jan 02, 2021
