Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passkeys are saved to default group even when custom default group is configured #2153

Closed
snwflake opened this issue Mar 20, 2024 · 2 comments

Comments

@snwflake
Copy link

snwflake commented Mar 20, 2024

Expected Behavior

Passkeys should either be saved to the default group set by the user for password credentials or it might benefit from having an alternative option dialogue to define a separate group for saving them.

Current Behavior

Saving a Passkey ignores the value set by a user in Saving Credentials -> Default group to save new passwords and saves it to KeePassXC-Browser Passwords regardless of what group the user specified in aforementioned option.

Possible Solution

Either apply the custom group name to saving the Passkey to said group, or introduce another text field in order to provide a separate group to save Passkeys in.

Tangent

I am fully aware that this is probably obsolete, once keepassxcreboot/keepassxc#10408 gets merged, but this is a bug regardless...maybe

Steps to Reproduce (for bugs)

  1. Set new default group for entries in the extension
  2. Create new Passkey

Debug info

KeePassXC - 2.7.7
KeePassXC-Browser - 1.9.0.2
Operating system: Linux x86_64
Browser: Chrome/Chromium 122.0.0.0 (Brave)

@varjolintu
Copy link
Member

Yes, I'm aware that option is not respected now. I think a separate option field could be used for this. I would assume users would like to use a different group for passkeys if possible.

@varjolintu
Copy link
Member

This change is required to the KeePassXC side for the feature: keepassxreboot/keepassxc#11260

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants