- Jul 02, 2020
-
-
-
For now the 2FA is cross browser, so the user can validate it through his browser.
-
In authorize url we need to add the nuser when it exists and we also need to add the good type_srv value (pro/part)
-
The TYPE_CARD account's number was NotLoaded
-
-
-
Attempts to access to ProAccountsPage can lead instead to RedirectPage. It would end up to a '/sites/erreur-404' URL (but in code 200). This happens only on certain connections, as a wrongly activated security feature of the server, as discussed directly with the bank, when there is no accounts on ProAccountsPage. If redirection was followed the whole session would be broken, without being logged out, tough. Need to log back.
-
The ELCLBrowser's subdomain is no longuer used and is now equivalent of LCLBrowser. Only the login page still function (to not mess with end-user habits I guess) but is not needed anymore.
-
When the investment's currency is different from the account's, the unitvalue is in the original currency, so we must fill obj_original_currency & obj_original_unitvalut instead of obj_unitvalue.
-
There is no need to Format() with 'Vente' or Achat', this information is already available with MarketOrder.direction
-
-
-
-
Transfers to newly added recipients require an authentication with a personal key card code and an app validation.
-
Some connections are in bug because we cannot fetch the user's information correctly on profile_page because of an Action Needed. The user has to fill-in and update its personal data on the wbesite.
-
sometimes the account is already signed in so we have to disconnect them
-
A 400 error can occur in the json we use to retrieve the saving accounts even if there are account to fetch so sometimes there are no reasons to this to happen.
-
ntome authored
-
ntome authored
HAR file was rewritten on every request, because JSON libs don't allow inserting data in an existing JSON without rewriting the whole file. However, if we put request/response entries at the end of the HAR data, only a fixed suffix exists after the entries. Then we can seek near the file end to a computed position, write the new entry (which overwrites terminators), and we can rewrite the overwritten terminators right after. Not only can we write only the new data, but we do not need to keep track of the shifted bytes. If the HAR wasn't written with the exact same options, we won't seek accurately though.
-
Add missing Account().number for "Compte Titre Ordinaire" account
-
A lot of connections are in wrongpass because they are in phenix browser instead of the main browser. We first do login with the main browser and in case of BrowserIncorectPassword we try on Phenix Browser.
-
If the amount of the transaction is too large, it is displayed in scientific notation. When that's the case, we fetch it in the details page of the transaction.
-
Life insurances are on a different space so it could cause an error.
-
The precedent code is kept in case of still used url.
-
on some accounts, csv is not available, it results to an empty history, so we need to get them in another way
-
we now get an otp when trying to get to much history : probably more than x months, so handle that case by bypassing this
-
Change the head_xpath and item_xpath of TransactionsPage
-
Attempts to access to ProAccountsPage can lead instead to RedirectPage. It would end up to a '/sites/erreur-404' URL (but in code 200). This happens only on certain connections, as a wrongly activated security feature of the server, as discussed directly with the bank, when there is no accounts on ProAccountsPage. If redirection was followed the whole session would be broken, without being logged out, tough.
-
The messsage seems to have change. It is now : "Vous n’avez pas de solution d’authentification forte. Pas de panique !". Moreover, we don't want to raise NeedInteractiveFor2FA if no 2FA is present.
-
One connection has an exact card's duplicate. This is a blocking state by default. Set ignore_duplicates in the related page's Elements solved the problem.
-
Links to accounts have changed slightly and the `ddp` parameter was not found.
-
-
-
-
-
-
If not the ID will be the main account ID and would an raise "There are two objects with the same ID" error.
-
-