- Jan 11, 2024
-
-
Also reworking a bit the process with iter_accounts and iter_investments. little change done on iter_history too. The website is a mess but we can have the pid sooner. We loose very little information.
-
- Oct 17, 2023
-
-
- Jun 01, 2023
-
-
Quentin Defenouillere authored
-
- May 23, 2023
-
-
Romain Bignon authored
-
- May 12, 2023
-
-
- May 02, 2023
-
-
AxaBanqueBrowser must go to a redirection bouncer to know if the user has his insurances on regular space or on outremer space. This bouncer is supposed to redirect us to specific URLs that allows us to know which space is used. Sometimes, it randomly gets the user to AxaAssuranceBrowser homepage instead of AxaAssuranceBrowser insurances pages. It can even happen when browsing on a regular browser. Going to insurances a second time seems to be enough to get the real redirection.
-
Instead of redefining __states__ in AxaBanqueBrowser, we keep the __states__ from cmso and add new states to it. It seems that states from cmso are still used for axabanque because a few 400 errors are triggered since a few weeks, making some connections fail at first synchronization.
-
If the user tried to synchronize within 5 minutes after a first synchronization, he would get a 401 because authorization token would not be set in the header (it is only set after regular login or SMS handling and not kept in the state). After 5 minutes, the STATE_DURATION would make the state expire and the user reconnect, making him have a new fresh token. Updated the STATE_DURATION to 10 minutes like it really lasts on the website and also skipped locate_browser to avoid loading URLs that must be accessed with the token, provoking 401 errors. Authorization could be stored in the state but then it would only be useful for users that need to do two synchronizations in less than 10 minutes. Instead, if they have to do this, module will relogin. refresh_access_token from parent allianzbanque can't be used for axabanque.
-
- Apr 14, 2023
-
-
Florian Duguet authored
-
- Apr 08, 2023
-
-
Romain Bignon authored
-
- Mar 28, 2023
-
-
- Mar 05, 2023
-
-
Romain Bignon authored
-
- Feb 12, 2023
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Feb 11, 2023
-
-
Romain Bignon authored
-
- Feb 04, 2023
-
-
Romain Bignon authored
-
- Jan 29, 2023
-
-
Romain Bignon authored
-
- Jan 26, 2023
-
-
Response's dict after login submission can be like : '{"url":"/mosaique","isRedirect":false}' so we need to adapt to this format. Also need to handle new response when credentials are invalid.
-
We can't guarantee the order of iter_accounts. From that order depends which browsers will be called first (AXABanqueBrowser, AXABourseBrowser or AXAAssuranceBrowser). Some rare cases were not covered. For example if the user has a bourse account, then it is possible that we switch to the bourse browser first. Since no switching method was used in this bourse browser, if the user had an insurance account, bourse browser would try to get insurance investments or history through its own methods.
-
Axa has three spaces, insurances only, bank only and bank and insurances. For bank space users, insurances accounts were not fetched since they were located on the insurance space. Browser switching now correctly fetches these insurances. The tricky part is that insurance space can itself have two spaces (metropolitan and overseas territories). We can call some URL from the AxaBanqueBrowser to determine on which space we're gonna land. We keep this information in the state of the browser to pass it to the AxaAssuranceBrowser.
-
In the investments details page, the investment label has one more space than what we previously got: `JPMF Global Natural Resources A Acc EUR` instead of `JPMF Global Natural Resources A Acc EUR` This made us miss it when calling `fill_investment`.
-
- Sep 05, 2022
-
-
It seems that we can have an isincode with a letter in its 10 last characters. Manage empty table case on wealth.
-
- Aug 22, 2022
-
-
Axa recently changed their policy for passwords. Regex had been modified accordingly from accepting only 6 digits to accepting any alphanumerical character. Problem is that some user say they have special characters in their passwords and our current regex does not takes them so it has been updated to take a wider range of characters.
-
- Aug 08, 2022
-
-
- Jul 11, 2022
-
-
-
-
Since the end of June AXA banque changed their security policy regarding their users' passwords and it now requires alpha numeric characters according to their communication: "A compter de fin juin, nous renforçons la politique de sécurité de nos services afin de protéger vos données personnelles. Votre code confidentiel devra être modifié et respecter un format alphanumérique."
-
- Jul 04, 2022
-
-
Although browser is inheriting from CMSO, AXABanqueModule is a dedicated module, where 'code' and 'request_information' were missing in order to work with 2FA process made upward in TwoFactorBrowser.
-
It seems as though AxaBanqueModule has had the CapBankTransferAddRecipient capability without having any of its browsers implement the new_recipient method, or any equivalent method for that matter. This commit downgrades the capability of the module to CapBankTransfer to only support transfers to already created recipients.
-
- Jun 27, 2022
-
-
ntome authored
- Jun 22, 2022
-
-
ntome authored
-
- Jun 13, 2022
-
-
- Apr 29, 2022
-
-
ntome authored
-
- Apr 28, 2022
-
- Mar 29, 2022
-
- Mar 16, 2022
-
-
- Feb 28, 2022
-
-
IsinCode is now the only text() value present in that part of HTML code, so the regex is useless and was making the module crash
-