- Feb 12, 2020
-
-
The Attr()() returns a string, coerce to int.
-
While navigating, we fetch a token on differents places to access the website, but in some case we are unable to find it at given location, so I add one more url that works for almost all the cases.
-
-
On the bnppere module, some customers put letters + digits in their passwords, making the VK crash. However, if we remove these letters and there are exactly 6 digits remaining, we sometimes manage to log in. We cannot use a regex in module.py because bnppere has two browsers (Personeo & Visiogo) and the Visiogo website does not use a VK.
-
-
Summary transactions come from the parent checking account and their dates have no time, whereas card transactions had a time, making the comparison with sorted_transactions() crash. Since the times are just '12:00:00 AM', we exclude them in order to fix iter_card_history.
-
raise AuthMethodNotImplemented for the moment
-
Some transactions have no details but have a raw label which we can parse the type, category and label from.
-
It's not a mistake, there are really `AUTHENTICATION_FAILED` and `FAILED_AUTHENTICATION` ...
-
Even if the 30 is on the website, return NotAvailable ...
-
DateTime for date is removed because the time is always 12:00:00 AM. If the rdate is not found with the patterns, we try to set it to dateOperation if dateOperation is before dateValeur.
-
-
-
The string that we were fetching was not the right one.
-
SMS are sent with background worker. We avoid it.
-
Previous xpath didn't get every case, sometimes the tag was h3 instead of h2.
-
A logger named only "iter_accounts" was not explicit enough anyway.
-
-
All the performances (1 3 5 years) are available on this CPR details page.
-
-
The new login mechanism is like transfer authentication and use same URLs and pages. There is 'context' in json response to know if it's a login or transfer, but this key is not always here when authentication fail and we don't know if it's for login or transfer. Refactorize all authentication mechanism to have the context through the code.
-
Some invests have no diff value, but the website fills the associated json field with the investment valuation.
-
Error parsing was not done properly on LoginPage on_load() method. Different messages are used to inform user of AppValidation. Certain connections don't have 2FA enabmed yet, they might bypass it, or not.
-
Some transactions have a rdate in the future in their label, which cause the transaction rdate to be after the date.
-
-
Sometimes the website displays us a page asking us to validate something before being able to go to the market page.
-
-
The multi-accounts was not handled yet so I adapted the browsing and parsing to retrieve transactions & investments.
-
-
-
The previous xpath returned the asset category twice.
-
-
hydrargyrum authored
-
- Feb 11, 2020
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Feb 10, 2020
-
-
hydrargyrum authored
-
hydrargyrum authored
Specification ============= In a PSD2 law context, in order to avoid triggering 2FA SMS or app validation unexpectedly in a non-interactive sync, a mechanism was introduced. Modules will now receive a "request_information" key which can have a few values: - None if the module was started non-interactively, for example by a cronjob - {} (empty dict) if the module was started interactively, be in a user-shell, a graphical app or through an API daemon - a non-empty dict if the module was started interactively, within a PSD2 AIS context, to pass special HTTP headers authenticating the AIS, as required by the law A module can ignore this param if not needed. If it was started interactively, a module can safely raise BrowserQuestion/AppValidation and other exceptions like this, requiring user interaction to unblock weboob operation. If it was not started interactively, a module should refrain from visiting pages triggering 2FA challenges, as the user will not be able to respond them. In such a case, a module can raise NeedInteractiveFor2FA to stop operation before a 2FA challenge would be sent. An app can then leave a notification to the user telling them to operate interactively, as a challenge will pop. Technical ========= This might not be the best place to add this header though. load_backends cannot be used because we don't know about interactiveness yet. _do_and_retry is not so bad because this is where 2FA challenges are handled anyway.
-
- Feb 09, 2020
-
-
hydrargyrum authored
_do_and_retry is quite generic to handle errors like BrowserQuestion and retry after the "question" has been answered. But in some cases (like boobank's transfer command), the command code already handles the exception, and this would break them. So, let it be called by commands who desire it. "ls" is a good start, more can follow.
-
It handles: - BrowserQuestion - BrowserRedirect - DecoupledValidation
-
- Jan 30, 2020
-
-
hydrargyrum authored
It has the advantage it will not prevent to write the use-weboob-local.sh script if weboob-config fails.
-
