Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Passkey no longer working on Boursobank
Hello, I uses passkey since 2023 on Boursobank without any issues. Since a few days, I have a error that is displayed immediately (no loading or timeout) telling me that it timed out, the website s...
Hello folks,
Our developers believe that they've identified an issue where a low timeout value set by Boursobank is causing 1Password's passkey flow to fail. A fix has been coded and is currently available in the latest version of 1Password in the browser. Please update to 8.11.0 or later:
If you're still running into an issue after updating then let me know and I can help further.-Dave
Any news on this 1+ month issue?
It seems to also be broken on Nintendo side (https://accounts.nintendo.com)
1P_Dave
Moderator
ModeratorOur team is actively investigating the issue with Boursobank but I don't have any news to share at the moment.
We do have a different issue open for passkeys not working in Nintendo in Firefox, I'll add you to that issue as well.
-Dave
#34178
Oh come on, you've been "actively investigating" for close to two months now. I call that stalling, not investigating.
- 1P_Dave
I can definitely understand how an ongoing issue like this is frustrating. The issue was in our backlog for a time but I've been actively collecting and reviewing logs from affected users with our development team over the last week and half and we're making progress towards a fix.
The issue is more complex to identify and resolve than many other issues since we can't create a test account for Boursobank to reproduce the issue. If you're willing to help me collect some of the information needed then please send an email to support@1Password.com and include the following:
- A link to this thread: https://www.1password.community/discussions/1password/passkey-no-longer-working-on-boursobank/155417/replies/157659
- Which browser you're using.
- The following sentence: Please forward this email to Dave from the Community.
After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to locate your message and reach out to you there with steps on how to collect the information needed.Update June 20th 2025: No other information is needed and the team is testing a fix in the nightly version. See my post here.
-Dave
Sorry for acting frustrated and everything, but hearing the same stock answer for almost two months didn't sound so encouraging. Now if the matter is being seriously investigated, I'd be pleased to help with it. I'll be catching up with you tomorrow.
