Confer, an app and service for privacy respecting AI chat, tries to store its generated passkey into a password service (in my case: Bitwarden browser extension).
Currently it fails with Bitwarden due to “not supported by Bitwarden”, asking to use 1Password instead.
So, please, implement this feature request, so we do not need to migrate to 1Password!
leaving a post here to express interest in enabling passkey PRF, will be back to vote once my account gains enough forum trust.
@574 & @notSoClever — Welcome to the forum!
Hopefully you meant that you will be back to this thread when you have gained voting privileges, because if you leave the forum entirely and only return to check your trust level, then you will find that you are going to be permanently stuck at the “new member” level (without voting rights). Trust level promotion requires forum participation (by visiting various topics of interest to you, and reading the comments posted there).
Yes, you did. The answer is in your own screenshot. The “vote” button changes to “voted” after your vote is registered. Also, do note that you can click the “voted” button to remove your vote if you change your mind.
@grb’s approach is great for when you use up all 20 of your votes and want to find one to remove so that you can instead apply it to something more important to you.
I have to agree. This has become a vital feature for Bitwarden to support or I’ll also have to ditch Bitwarden and take my $ for me and my spouse to another provider. I also am unable to use it for Confer.to and as more sites focus on higher security levels, this puts Bitwarden closer to obsolescence.
Same here. I would really like to use confer.to, but that doesn’t work with the current system…
Added my vote and commenting to express my support for this feature request. Please add this to Bitwarden!
+1 Would love to use Confer.to
Another +1 for Confer.to
Welcome, @leerentveld and @F8f2y4MQGxJCCTcT to the community!
The proper way to show support for a feature request is to browse various topics on the community for about 30 minutes. Once you have shown interest, you will be raised to the “basic user” (from “new user”) trust level and will be given 20 votes. Then, return to this topic and click the blue vote button at the top.
I was really disappointed to see that Bitwarden wasn’t supported by Confer.to in particular. I’ve voted for this topic, but just wanted to point out that it’s this specific use case that brought me here.
Voted, I also discovered bitwarden is not supported for Confer.to. Bitwaren support stated
“After further investigation the reason why Bitwarden does not function with the confer.to website is because Bitwarden does not currently support saving of PRF passkeys, we do have an active feature request for this functionality though. I’ll provide a link below.”
hence joining and voting for this. I hope this is implemented.
Really looking forward to this. I’d rather not use a different manager for these cases, like Confer.
I’ve seen that confer.to is not accepting as Bitwarden to store its PRF based passkey. Please implement this feature. Don’t want to switch to 1Password just for this issue
Adding my vote for confer.to and filekey.app as well.
I would also like to see Bitwarden to support storing PRF, but until then it should give a proper error response when creation of a Passkey with PRF is requested.
Now it will silently continue as if it worked but you’ll find out it didn’t when you actually try to use them. While my old Yubikey (that predates PRF and thus doesn’t support them) will cause an error indicating that the passkey couldn’t be created in the first case.
The website, https://choggiung.com, already has the feature utilizing PRF with other passkey storage systems, but we have settled on BitWarden as our company standard. Thus, we need it to support PRF data storage for our website users who could then have private data stored on the server encrypted by PRF key derived from their browser and synced with other browser via BitWarden. Then, users could migrate access to their PRF-encrypted data between browsers and devices simply by utilizing BitWarden’s passkey sync.
c’mon Bitwarden the people have spoken where’s the PR to implement? let’s gooooo
