Fong NGO authored Jan 08, 2021 and hydrargyrum committed Feb 12, 2021

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.

Fong NGO authored Jan 07, 2021 and hydrargyrum committed 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.

Fong NGO authored Jan 07, 2021 and hydrargyrum committed Jan 27, 2021

The message should help the user understand he didn't choose the proper
website (pro instead of par).

Fong NGO authored Dec 14, 2020 and hydrargyrum committed Jan 09, 2021

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...

Fong NGO authored Dec 14, 2020 and hydrargyrum committed Jan 09, 2021

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).

Maxime Gasselin authored Mar 17, 2020 and hydrargyrum committed Mar 18, 2020

We returned a false browserunavailable in some pro accounts. Here
we add a check on the redirect page.

Closes: 56215@sibi, 17824@zendesk, 17830@zendesk, 17844@zendesk, 17854@zendesk, 17858@zendesk, 17863@zendesk, 17868@zendesk, 17871@zendesk, 17905@zendesk, 17923@zendesk, 16614@zendesk, 17943@zendesk, 17957@zendesk, 17966@zendesk, 17971@zendesk

Guillaume Risbourg authored Nov 25, 2019 and hydrargyrum committed Jan 08, 2020

The is_here on ProAccountsList caused the errors to not be catched.
New ActionNeeded error catched in ProAccountsList.
New BrowserUnavailable error catched in the RedirectPage.

Damien Mat Jedrzejewski authored Jul 30, 2019 and hydrargyrum committed Aug 28, 2019

Closes: 12426@zendesk, 12702@zendesk

Damien Mat Jedrzejewski authored Jul 16, 2019 and Romain Bignon committed Jul 27, 2019

Needed to rewrite the parsing for the pro website.

Closes: 43620@sibi

Quentin Defenouillere authored May 15, 2019 and Romain Bignon committed May 19, 2019

Some connections are in crash because there are <!-- --> comments in
the 'td' tag of the balance: using .text_content() solves the issue and
return the correct balance.

Closes: 41316@sibi

Maxime Gasselin authored Feb 12, 2019 and Romain Bignon committed Mar 16, 2019

The next_page navigation is totally illogical. In the next page button
you can return to the first transactions. Morever no logical pattern in
history url navigation can be exploited. Nevertheless, we can skip
these pages with the comparaison of the first transaction of the page.

Closes: 8257@zendesk 8318@zendesk 8292@zendesk 9235@zendesk 9589@zendesk

All copyright holders have given their consent.

Sylvie Ye authored Mar 22, 2018 and Romain Bignon committed Mar 31, 2018

Closes: 580241@redmine

ntome authored Apr 19, 2017 and Romain Bignon committed Apr 27, 2017

bforbank, boursorama, bp, cragr, spirica

Vincent Ardisson authored Dec 13, 2016 and Romain Bignon committed Dec 24, 2016

No declarative code is used yet though