- Mar 17, 2024
-
-
Ludovic LANGE authored
current implementation of `iter_history()` is inherited from `cmso` ; and is calling the `/domiapi/oauth/json/accounts/detailcompte` API. With this API, the transactions details seems incomplete for the first six weeks (missing ID in particular), which is already known per the comments: https://gitlab.com/woob/woob/-/blob/master/modules/cmso/par/browser.py?ref_type=heads#L526-527 We now use the same API as `allianzbanque`: `/distri-account-api/api/v1/persons/me/accounts/XXXX/transactions` which doesn't suffer from this issue. Note that among multiple APIs, the `id` field of a transaction is right-padded with either '_' or '=' ; so we remove those trailing characters in order to have an easier way to compare those ids.
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
-
Ludovic LANGE authored
`cmso` is used for some bank modules - those for which the web interface is based on Arkea's APIs. In the case of `ccf`, some of these pages do not exist. To keep from duplicating code, we found it was better to handle this at the `cmso` module level.
-
- Feb 19, 2024
-
-
at bank side. In order to deliver something as soon as possible, some features / support are removed : - All capabilities except bank account list and bank hisotry list - Naxatis, Credit Maritime support (I don't have account to test it) I also expect all other subbank working because the backend is now unified and the only change seems to be related to cdetab parameter.
-
at bank side. In order to deliver something as soon as possible, some features / support are removed : - All capabilities except bank account list and bank hisotry list - Naxatis, Credit Maritime support (I don't have account to test it) I also expect all other subbank working because the backend is now unified and the only change seems to be related to cdetab parameter.
-
at bank side. In order to deliver something as soon as possible, some features / support are removed : - All capabilities except bank account list and bank hisotry list - Naxatis, Credit Maritime support (I don't have account to test it) I also expect all other subbank working because the backend is now unified and the only change seems to be related to cdetab parameter.
-
at bank side. In order to deliver something as soon as possible, some features / support are removed : - All capabilities except bank account list and bank hisotry list - Naxatis, Credit Maritime support (I don't have account to test it) I also expect all other subbank working because the backend is now unified and the only change seems to be related to cdetab parameter.
- Feb 13, 2024
-
-
It seems the page to choose the 2FA method (u2f, totp, ...) has changed a little bit, while other page still use the previous layout. We now handle both (form name, message).
-
-
OVH lets the user enable (or not) a 2fa, which is used during each regular login. It's now possible to manage this 2fa with 2 new (optional) config values: * `2fa_type` let you choose the type of 2fa (between `totp`, `sms`, `u2f`, `staticOTP`) * `2fa_value` let you handle the value of this second factor. You have multiple options for the value of the 2fa: * You may let `2fa_value` absent or empty, in which case weboob should ask you for the value to use at the time it is needed. You'll be able to use your TOTP (mobile) application, check your received SMS, use a security code, ... * You may also choose to use an external tool which will provide the value (e.g. PasswordStore with OTP extension, an SMS reading application, ...) Note: For the moment, the 'u2f' method needs specific information sent to the key which are not available in this interface (challenge, list of registered keys). Please do not use it at this time. Note: OVH sometimes chokes when forms are sent too frequently. As the 2FA handling needs to submit at least one or two forms, we slow down things a bit with a sleep() call.
-
- Feb 11, 2024
-
-
Théo Le Calvar authored
-
Ludovic Rousseau authored
The power data for horly may also be for each 15 minutes. The module now supports both half-hour and quarter-hour measures.
-
Rémi Nivet authored
-
- Feb 08, 2024
-
-
- Feb 06, 2024
-
-
Thomas Touhey authored
* Fix login and logged in detection. * Fix navigation for all users. * Fix multiple daily picrosses management for premium users. * Fix solving with hidden form detection.
-
Thomas Touhey authored
-
-
DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html Also, it required setuptools to be installed, which was not specified in requirements.
-
- Jan 29, 2024
-
-
Thomas Touhey authored
-
- Jan 11, 2024
-
-
-
-
URL to get bnp's investments details has been crashing randomly for years with random 503. This is still the case except that now, on the website, this 503 takes up to two minutes to be triggered. The module's timeout set at 60 isn't even enough for this. Rather than making very long synchronization, we now assume that 30 seconds timeout on this specific request is enough to consider the details as unavailable.
-
SNID is necessary at some point during the login process. We must fetch it in a javascript that has a bit changed. Did some factorization so that each child module uses the right SNID, even though the website seems to be accepting the CE SNID in most cases.
-
Life insurance with label 'Epargne Compte Libre Croissance' has only one investment and there is no more information on detail page so we create an invest with the account information.
-
When trying too close reconnections, the user account can be blocked. This connection status was not handled.
-
All URLs that had "ensu" in their URL path dropped it.
-
The 'Compte Syndicat Copro Travaux' type is savings although the website shows them as checking accounts.
-
-