- Apr 26, 2021
-
-
-
-
Despite its name, 'CAPI_AGF' is a life insurance. There are no capitalisation contracts on the website.
-
This reverts commit dc99d31a718ee500d0c5adfbb96a2b5721af992f.
-
- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 04, 2021
-
-
- Mar 24, 2021
-
-
- Feb 26, 2021
-
-
Some market orders have no quantity and are instead some sort of subscription. The amount label in the table is also a bit different so I adapted that as well.
-
When reloading state and requesting the last page visited, we are usally logged out. If that page was EasyTransferPage, in that case, it is now a JSON, instead of the regular HTML when already logged. This is now handled with a special logged property.
-
- Feb 12, 2021
-
-
When reloading state and requesting the last page visited, when that page is one of the one in json_pages.py, we are usally logged out. This is handled in AccountJsonPage with a special Logged property. But it needs to be as well in the other pages. We do that by introducing a LoggedDetectionMixin, inherited by a SGPEJsonPage, common to all subsequent pages.
-
To better avoid problems when changing things not common to SGEntreprise and SGProfessional, inheritance scheme is changed. A common SGPEBrowser still exists. It takes in common login steps from SocieteGeneraleLogin, and common Pro/Ent navigation. But SGProfessionalBrowser and SGEnterpriseBrowser are now each inheriting separately from SGPEBrowser. It bears importance for the few differences in 2FA handling for Ent, where it is systematic, compared to Pro. Also, dead code is deleted (browser and pages' side). And a few commenting is added.
-
Initially only the case of "PLAFOND_SIGNATURE_DEPASSE" had to be added. But after discussions, the need to fix other cases emerged.
-
-
Secure Access is a kind of AppVal and is the 2FA method for Ent users. It was implemented with the common SocieteGeneraleTwoFactorBrowser. But it a systematic 2FA and it could not work with the backend for several reasons: - when entering the handle_polling, first URL to be called, when loading state, was initiating a second 2FA; - only one user's device name was displayed in the validation prompt, although there could be several; - after validation, we must to end up on a LoggedPage to avoid triggering a chained init_login(); - once in background sync, load_state was starting at last url, altough it needs to start at login to be able to raise NeedInteractiveFor2FA; - also, since SGProfessionalBrowser is inheriting from SGEnterpriseBrowser, we must be revert in it some of the discussed changes made in SGEnterpriseBrowser.
-
- Jan 27, 2021
-
-
-
The previous one now leads to a 302. Arrival page is still the good one to parse accounts.
-
Previously we were getting the transactions of the deffered card on the comings of the main account
-
- Jan 18, 2021
-
-
hydrargyrum authored
Sometimes there are no transactions for 3 months, it's acceptable. However 4 pages (1 year) without transaction is rarer.
-
hydrargyrum authored
-
-
The iban is now directly accessible with the main account json, and so, there is no need anymore to load the transfer page to get the iban. Also, if fixes the issue of iban not being available for accounts that were not allowed for transfers.
-
-
- Nov 27, 2020
-
-
Damien Mat Jedrzejewski authored
Ent browser has been properly separated from Par browser in a previous commit. They now only share login part through a separate login class. But the module globally calls for iter_market_orders, which has sense for Par and Pro, but not for Ent.
-
Damien Mat Jedrzejewski authored
-
Damien Mat Jedrzejewski authored
2FA has been activated for Entreprises clients. We can abstract Particuliers handling of TwoFactorBrowser, the same way it is done for Pro clients. Also Pro and Ent browsers needed some refactoring. Common login part in SGPEBrowser now uses login and 2FA handling from Par browser for both.
-
- Nov 17, 2020
-
-
These accounts were mistakenly typed as checking accounts.
-
- Oct 28, 2020
-
-
The value is the same than par website. Without that we get nok after sending otp and user cannot validate the sca.
-
Done with commit 4aeb7016c1e1c851f45a7a00d9315a28b576b1b0: No message is provided by the login API in cases of ActionNeeded. In order to help out clients I controlled the meaning of those, by connecting in a navigator and collecting the JS-forged messages. A logger and 2 types of messages were added. This commit: One final message is now added. Logger is modifed to return only bad login cases
-
-
No message is provided by the login API in cases of ActionNeeded. In order to help out clients I controlled the meaning of those, by connecting in a navigator and collecting the JS-forged messages. One message is still not found, so I put a logger to do so.
-
- Sep 09, 2020
-
-
The grid data is now handled seperatly between pro and ent.
-
like the commit 4a2987a9727756baf57a3934fb502e14a94be533 In PSD2, the account id is the "identifiantPrestation" when the account id is "codeGuichet+numeroCompte" in website and the transfer_check_account_id will be False because of that In this case, we just need to check the "codeGuichet+numeroCompte" part in the "identifiantPrestation".
-
in order to also retrieve recipient for PSD2 accounts. In PSD2, the account id is the "identifiantPrestation" when the account id is "codeGuichet+numeroCompte" in website
-
- Aug 26, 2020
-
-
Also boursorama
-
-
- Aug 07, 2020
-
-
-
URL changed and it is now a JsonPage
-
Now Pro browser uses same decoding needed for Par browser
-