- Apr 26, 2021
-
-
-
The login process has changed on bnp, at least the old method we used is now deprecated. The error message on login is now dynamic.
-
During login we have multiple redirections. We can catch future otp information between 2 redirections. Seems to be needed here just for pro accounts.
-
New url must be catched: https://pro.mabanque.bnpparibas/fr/secure/100-connexions. Consequently a more global url has been added for all 100-connexion cases. Moreover this request can lead to a 302 and on_load must be forced with an allow_redirects=False.
-
- Apr 11, 2021
-
-
Romain Bignon authored
-
Romain Bignon authored
-
- Apr 08, 2021
-
-
Sometimes after login process the server redirect to an url ('/fr/systeme/page-indisponible') which belong to urls used to indicate that the password has expired, even when it doesn't. In such cases BrowserPasswordExpired is raised inconsistently to users. Getting rid of this url fix that problem and the erratic redirection of bnp doesn't affects users pathways since it occurs after the login.
-
The url to search documents based on the accounts has changed on the bnp website.
-
- Apr 04, 2021
-
-
- Feb 26, 2021
-
-
When the otp step was not completed or failed, a recipient was still created on the bnp website with the "to be activated state". It was not possible to do more than a single otp code attempt without going into an unexpected state. And trying to add again the recipient would fail with the following error: "Bénéficiaire en doublon. Code bic / iban / compte déjà présent en base." This change will detect if the recipient already exists in a "to be validated" state, and in that case will just trigger the activation otp or decoupled instead of trying to add the recipient again.
-
- Feb 12, 2021
-
-
If we are going more than 2 times to the login page of bnpparibas and that we are already logged in, the server has a bug and starts to go into a redirect loop. (Note: This does not appear to be the case for Hellobank).
-
- Oct 28, 2020
-
-
hydrargyrum authored
-
-
- Sep 23, 2020
-
-
It fails with utf-8-bom.
-
- Aug 26, 2020
-
-
New recipients are activated, at most, 1 day after being added.
-
- Aug 07, 2020
-
-
The password requirements have been updated. Before, no more than 2 digit repeats. Now you need at least 3 different numbers.
-
- Jul 15, 2020
-
-
-
-
modify the withdrawal regex to make fields optional in case the original wording is just "RETRAIT DAB" without the other fields.
-
-
hydrargyrum authored
-
- Jul 02, 2020
-
-
For now the 2FA is cross browser, so the user can validate it through his browser.
-
- Jun 17, 2020
-
-
-
-
It is cleaner to use MapIn for this kind of typing.
-
-
For now the SCA is crossbrowser, so the user can validate the sca through his browser.
-
After modifiying the password, there is a call to another URL that is done by the website to validate the password change. The message returned by the json can variate, so we need to check if there is an error based on the statut returned, not the error message.
-
- Jun 03, 2020
-
-
Use a generic CANCELLED status
-
- May 07, 2020
-
-
-
Closes: 58573@sibi
-
-
FACTURE"
-
- Apr 22, 2020
-
-
-
For some connections the NatioVie spaces does not exist and lands on a 302 trying to redirect to an unexisting page (/NSFR?Action=DSP_VGLOBALE). We handle it with allow_redirects=False & PartialHTMLPage.
-
- Apr 08, 2020
-
-
before digital key was handled with BrowserQuestion, now use the AppValidation because digital key is mobile app validation mechanism
-
-
This reverts commit a9a51055891af929b87da96825e1b36cf9567d72. Since the SSL certificate was renewed, the capitalisation_page is now reachable, and the SSLError bypass is no longer needed.
-