Boursobank and france identité not working on iodé 6.8

System and Apps
21

So I just reinstalled IodeOS on my FP4

I do not have no seedvault backup with boursobank on it, so I tried ro reinstall it through aurora store.

When I try to log in, I get the error message that the app does not come from the Play store and find myself unable to log in (several attempts).

Then I uninstalled the app and tried the above proposition

Aurora store > settings > install settings > choose microG install program (third choice)

Without success, I could not log in.

I also tried to reinstall boursobank app after modyfing Aurora store > settings > network > google play version > choose latest (third choice) without any more luck.

I cleared boursobank storage before each uninstall/reinstall attempt.

I trided to combine these tweaks with the one that is mentionned earlier in this thread (disabling microG)

Any other idea to make boursobank work on IodeOS?

22

Mhh I see it’s seems quite complicated..

I’ve an idea :

  • Install it with whatever method
  • Do a specific seed vault backup only for the BoursoBank App
  • Uninstall it
  • Restore it through the backup

Maybe it can work?

23

I don’t know if it will help but the LineageOS for microG project wiki, now has a page about banking apps. It includes a section on how a user got the BoursoBank app to work by using Shelter.

https://github.com/lineageos4microg/l4m-wiki/wiki/Using-Banking-apps-with-LineageOS-for-microG#boursobank

24

I tried this and it did not work, boursobank app does not let me connect to my account and display an error message instead

25

Tried this also (only the last steps with shelter, not the part with recovery changes) and it did not work

26

Hello

I finally installed the last CalyxOS test build and succeeded to make boursobank work on it.

MicroG services installed, but had to be disabled to log into my account, as per the tip provided higher in this thread.

Logging in to my accound, I had to perform an identity check and provide a picture of my ID and video selfi.

Then, I re-enabled microG services and can still log in.

27

Happy to hear you you got it connected, but this is a bit strange to sort out. Newest Calyx builds I believe are also now LineageOS based (?? I may be wrong on this??), and also use microG, so they really should be in a similar compatibility situation?

28

Calling Boursobank and asking them to “retirer mon appareil de confiance” lets you validate transfers and 3D Secure payments using an SMS and email code instead !

It took less than 10 minutes in my case.

Here is a direct link to request a callback from them, which also avoids having to go through the chatbot.

Just be aware that logging back into the app (after the Face ID and identity verification) automatically re-enables the trusted device and disables the SMS/email authentication again.

29

Thanks for the followup! This workaround will be helpful for several, I think!

30

Thank You very much! Thar was so helpfull! After 3 months trying to solve that dilemna :folded_hands::folded_hands::folded_hands::folded_hands:

31

For anyone wanting to have the boursobank app instead of going back to SMS code.

There is a workaround who work for me on a new install on a fairphone 5. It’s on /e/os forum :

Please be aware that the app is exclude from the blocker with this method. And that there is known tracker in this app :

32

I am a bit confused: basically they are advising to ‘disable microG services’ to complete Boursobank authentication. After authenticated, then can later re-enable microG? I prefer running my banking app in a Shelter profile as well (to keep it frozen most of the time) but it seems if the problem is only microG “attempting to help” that the various features of it could be disabled temporarily and then the user would get the same result as with the “Shelter freeze microG” trick?

Note: The iodé blocker works at a system-wide level meaning it is active for Shelter / Private Spaces / etc. But you are correct the graphical interface (iodé app) would not “see” / “report” on the app in question, as the iodé app runs at the user level (so you only see apps from the main profile). So it is a bit of “blind blocking” but is still used. On the dev “to do list” somewhere is intention to re-work this.

33

As I understand, the trick is to forces the app to relay on a web authentification for the first one. Can we do that outside of shelter ?

I didn’t know that the blocker is still working with shelter, it’s good to know. I had problem in the past with this app and rethinkdns where the only way to make it work is to tell rethinkdns to not monitor the app, just allowing traffic didn’t work. So there is some kind of security in the app if it’s too much monitoring.

34

Thanks for the likn. I got called back, explained my situation, kindly asked for suppressing my trusted device (or replace it with yubikey), was put on hold … and disconnected (and never called back). This tends to support the hypothesis that these banks have every interest in ensuring their customers continue to use their apps. No surprise.

35

Oddly enough, the workaround was effective with my S10e running e/os (despite unlocked bootloader) and failed with a pixel 4a running iodé (despite locked bootloader).

36

Using the ‘Shelter freeze / unfreeze shuffle’? By “failed” on iodé do you mean it didn’t attempt to open the link correctly to allow you to authenticate or?

37

On e/os : indeed, using the freeze procedure was effective.

On iodé : I could not pass through the first login, ie once I launch the app from within shelter. I got the integrity device something message.

38

My mistake. I get the oups! screen of death, saying that the app is not from the Google play store (I just tried again with my newly turned pixel 6a. Obviously I used and freezed aurora store rather than the app lounge from e/os, and an anonymous session.

39

I am a bit unclear of the implication: so does this mean that /e/OS and iodéOS are behaving the same, and you can not get authenticated with either now?

40

While implementing the workaround: I can log in with e/os but I cannot with iodé.