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 switch directly to a normal login.
So I guessed there was an issue on the key itself.
I tried to revoke and create a new one, but same issue. When trying to create a new passkey, 1Password display the error "The request to create a passkey timed out". The error is also immediate (no loading or anything).
On the website, it displays "Enrolment has expired or been cancelled".
I've tried using other passkeys I have, without any issue. It seems to only impact Boursobank.
Using Firefox 138.0 + Extension on Windows 11 24H2
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
75 Replies
Any news on this 1+ month issue?
It seems to also be broken on Nintendo side (https://accounts.nintendo.com)
- 1P_Dave
Moderator
Our 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.
There is no workarounds, I need to "clic" my password, and this is a regression on my usages !
We are still waiting. Any news ?
- 1P_Dave
I'm sorry for the impact that the issue is causing. Have you tried either of the workarounds that I mentioned in the pinned post in this thread? If you have an iPhone or Android device, you should be able to save and sign in with a passkey using 1Password on that device by choosing the option to scan a QR code on your desktop device using your mobile device.
Let me know if that option doesn't work.
-Dave
It's kinda funny to see "solved" on this thread, when the issue isn't solved. "Answered" would make more sense, if that's how it's meant to be understood.
Not sure it is on the bank side, as Apple keychain is working fine
Hello
It's almost 1 month now (I waited a couple of days before raising the issue).
- Do you have an estimated time of resolution?
- Do you have more information of the issue itself?
Really discouraging, been encouraging family & friends to use your product, and I'm going passwordless when able.
But if the software is not reliable and communication is so minimal without clear indicator of what is going on, when it is going to be fixed, I'll maybe also look to switch product.
I've tried another workaround : use apple solution, you now what : it is working fine, and I think I'll use it and leave 1 password after more than 10 years of use, because sorry but such a bug and so long without any correction is not acceptable.
Shame. This isn't the only issue and it seems relatively young compared to a few other bugs that have lived long--for example, being prompted for Windows Hello auth after unlocking vault using the password--and there is no clear roadmap to squashing them. Really unfortunate.
hello, any update on this ?
- 1P_Timothy
Community Manager
Hi jro! No updates to share at this time.
Quite long and disappointing for this kind of regression on a subscribed software…
Same here with 1Password for Mac 8.10.75; tried on Brave and Safari. I revoked the key and tried to create a new one but got the same "The request to create a passkey timed out." error
Hello,
I've sent the email, as requested.
I removed the message flagged as a solution, as the error is still there.Cheers,
- 1P_Dave
Thank you for sending in the diagnostics report, the team has identified this as a known issue as summarized here. Hopefully it can be fixed soon and I'm sorry for the inconvenience.
I removed the message flagged as a solution, as the error is still there.
Just to clarify, marking a post as a solution to a thread doesn't mean that the issue/request itself is fixed or closed. It's a way to highlight the most up-to-date answer for anyone who is running into the same issue and stumbles onto the thread so that they don't have to read the entire thread looking for the latest information.
-Dave
I see. Thanks for the clarification 👍
