- Apr 26, 2021
-
-
For some deferred cards, LBP doesn't provide any "encours" amounts.
-
- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 08, 2021
-
-
- Apr 04, 2021
-
-
- Mar 12, 2021
-
-
For cards without transaction summary, create a fake summary transaction from the card's coming value.
-
Some deferred cards do not have transaction history and can even make the website crash if we try to access it. It seems to be linked to whether the card is from a third party account or not. In any case retrieve the card details via an API call, not via the transaction summary page.
-
We couldn't retrieve cards anymore because the pages changed slightly
-
- Feb 26, 2021
-
-
In this particular case, if we get the "unavailable website" message, we want to try to fetch invests on the other life insurance page.
-
For par accounts' loans, the XPath to get the currency is sometimes different.
-
- Feb 20, 2021
-
-
Romain Bignon authored
-
- Feb 12, 2021
-
-
The banque postale website often has temporary unavailabilities of pages. When it happens, instead of being redirected to a specific url, the content of the page is simply rewritten with an unavailability message. Closes: 186382@sibi 155183@sibi 145247@sibi
-
Here are exemples of labels that were returned for coming transactions: data-titrepopinv2="Détail d'une opération" >PREL D data-titrepopinv2="Détail d'une opération" >FR6720 data-titrepopinv2="Détail d'une opération" >200410 It should have been: PREL DE MATMUT ROUEN FR672045353464765875867865556435 200410414141414141414343 The previous code was not working well because there are two "<a>" elements, one at the root and one inside a "<noscript>" element. Sadly the one inside the noscript element is kind of broken: <a class="popinV3" href="../../comptesCommun/detailoperation/operation-detail_operation.ea?idxOperation=0&typeOperation=OAV" target="_blank"> data-titrepopinv2="Détail d\'une opération" >PREL DE MATMUT ROUEN The a element is incorrectly closed after "blank" and the real end symbol is escaped. To be noted: this way to extract the transaction is only related to coming transactions. For normal history, the line content is extracted by the previous part of the code, and is based on a span element and no "noscript".
-
-
Previous commit revealed new 2FA messages. that where silenced by an ActionNeed. Here it is a Certicode Plus auth method that actually needed to be triggered.
-
Previous commit revealed new 2FA messages. that where silenced by an ActionNeed. Here it is a Certicode auth method that actually needed to be triggered.
-
I have managed to find a pro connection with a wealth account (a compte titre). Adapt the code for the new website to fetch investments / history of wealth accounts. Follows the rework of LBP pro website: 97968cde1b646cb05f97ae33489440c5979b9256
-
Related to rework of LBP pro website: 97968cde1b646cb05f97ae33489440c5979b9256
-
Related to rework of LBP pro website: 97968cde1b646cb05f97ae33489440c5979b9256. Login was fixed in a previous commit so I can now access more connections (and especially connections with savings accounts) more easily.
-
-
For saving accounts (livret), the following entries were not recognized by the transaction pattern matching: INTERETS ACQUIS DECOMPTE D'INTERETS INTERETS BRUTS ACQUIS DECOMPTE D'INTERETS
-
-
My accounts had the ownership incorrectly reported as "Attorney" instead of "Owner". The root cause is that the name fields in the profile page are all in uppercase but in the account name they are capitalized.
-
2FA are skippable for some users. This is properly handled when 'no2fa' message is detected. But in this new case, since message was not acccounted for, 'no2fa' status was not attributed, and so skipping URL wasn't even searched for. Now, new message is added. Plus, if 'no2fa' is not attributed, in last resort, we check if a skipping URL is present. That way we can detect new cases instead of raising a wrong ActionNeed to user.
-
- Jan 27, 2021
-
-
-
Also, add logs in case we find a connection with a required 2FA so we can use it to implement 2FA later on.
-
The message should help the user understand he didn't choose the proper website (pro instead of par).
-
Some connections still have the old layout so we need to handle both.
-
There have been several design changes on the accounts pages, so a lot of xpaths had to be updated. The navigation seems unchanged.
-
- Jan 18, 2021
-
-
- Jan 09, 2021
-
-
-
Sometimes the details page is not yet accessible for some accounts. Prevent crashing in this case.
-
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).
-
- Dec 11, 2020
-
-
Only 10 numbers and an optional 11th number or letter are allowed.
-
They change again...
-
