Skip to content
  1. Jan 11, 2024
  2. May 23, 2023
  3. Apr 08, 2023
  4. Mar 05, 2023
  5. Feb 12, 2023
  6. Feb 11, 2023
  7. Feb 04, 2023
  8. Jan 29, 2023
  9. Jun 27, 2022
  10. May 09, 2022
  11. Nov 24, 2021
  12. Oct 13, 2021
    • Stéphane Sobucki's avatar
      [n26] various fixes after module rework · 55b5914e
      Stéphane Sobucki authored and hydrargyrum's avatar hydrargyrum committed
      Fixes:
      - Correct typo introduced in 960ee9a4f2056e08248c4da663fdd15e26972e79
      when getting the ClientError's status_code attribute.
      - Also to be safe, we clear the mfaToken so that it's not reused
      in future 2FA session.
      - Transactions can indeed have no label (as it was done before the
      rework)
      55b5914e
    • Stéphane Sobucki's avatar
      [n26] rework the module · 8eef8212
      Stéphane Sobucki authored and hydrargyrum's avatar hydrargyrum committed
      Rework module using the TwoFactorBrowser, in order to make
      the module easier to debug.
      
      What's new:
      - The AppValidation 2FA method was implemented as it is more robust
      as N26 has stated in their documentation. This method is used as a
      default and we fallback to OTP by SMS if the user hasn't paired its
      device.
      - Added Pages instead of doing everything in Number26Browser
      - Replaced `request` method by `build_request` as
      it was only used to set the headers
      - flake8 compatible
      
      Fixes:
      - Using an access token generated using the refresh token
      gives access to 90 days of transactions only.
      - Too many requests error sometimes don't return a json body.
      - Clear access_token on 401 errors
      8eef8212
  13. Jul 23, 2021
  14. Jul 01, 2021
  15. Jun 30, 2021
  16. Apr 11, 2021
  17. Apr 04, 2021
  18. Jan 09, 2021
  19. Dec 11, 2020
  20. Nov 25, 2020
  21. Jul 02, 2020
    • Augustin Bouverot's avatar
      [n26] Handle 405 errors · 7d42703d
      Augustin Bouverot authored and ntome's avatar ntome committed
      We can randomly get a 405 error back from our first request in the
      do_login(), causing a crash while trying to parse the empty response body
      as json.
      7d42703d
  22. Feb 12, 2020
  23. Feb 11, 2020
  24. Dec 05, 2019
  25. Nov 20, 2019
  26. Nov 09, 2019
    • droly's avatar
      [n26] Handle more error cases · 89212a8c
      droly authored and hydrargyrum's avatar hydrargyrum committed
      I've handled some errors in the login requests.
      
      closes: 50309@sibi
      89212a8c
    • droly's avatar
      [n26] Rework login, Handle OTP and refresh_token · 98507d00
      droly authored and hydrargyrum's avatar hydrargyrum committed
      Since n26 added new SCA on its app, their can be only one device paired to an account, other devices will be asked an OTP each time they try to log.
      
      By reversing the app i found that we can use the 'refresh_token', but since it's not used by the app it might be removed.
      
      closes: 13368@zendesk, 13367@zendesk, 13349@zendesk, 13366@zendesk, 13360@zendesk, 13413@zendesk, 13439@zendesk, 13462@zendesk, 13523@zendesk, 13526@zendesk, 13527@zendesk, 13562@zendesk, 13613@zendesk, 13681@zendesk, 13687@zendesk, 13692@zendesk, 13728@zendesk, 13739@zendesk, 13854@zendesk
      98507d00
  27. Mar 16, 2019
  28. Feb 27, 2019
  29. Feb 24, 2019
  30. Feb 05, 2019
  31. Jan 06, 2019
  32. Oct 11, 2018
  33. Sep 16, 2018