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

[BUG] When having mutliple Databases opened KeepassXC asks twice in which one a new Passkey shall be stored #10602

Closed
sahriVoraus opened this issue Apr 19, 2024 · 1 comment · Fixed by #10609

Comments

@sahriVoraus
Copy link

sahriVoraus commented Apr 19, 2024

Overview

When you want to create a new Passkey with two databases opened at the same time the dialogs will look like this:
Select the Database
Screenshot 2024-04-19 093644
Register the Passkey
Screenshot 2024-04-19 093652
Again select the Database:
Screenshot 2024-04-19 093701

Steps to Reproduce

  1. open two databases
  2. connect both to the browser plugin
  3. enable Browser settings like shown in context (The setting "Search in all databases" doesn't seem to affect the passkey behavior. When I have two databases opened I will always be asked in which one I want to search for the passkey or where to store it. Maybe another bug?)
  4. add a new Passkey for example for https://www.passkeys.io/

Expected Behavior

I expect to only get asked at the beginning

Actual Behavior

You have to select the database twice

Context

My KeepassXC Browser Integration settings:
image

KeePassXC - Version 2.7.7
Revision: 68e2dd8

Qt 5.15.11
Diagnosemodus ist deaktiviert.

Betriebssystem: Windows 11 Version 2009
CPU-Architektur: x86_64
Kernel: winnt 10.0.22631

Aktivierte Erweiterungen:

  • Auto-Type
  • Browser-Integration
  • Passkeys
  • SSH-Agent
  • KeeShare
  • YubiKey
  • Schnelle Entsperrung

Kryptographische Bibliotheken:

  • Botan 3.1.1
@varjolintu
Copy link
Member

A database selection is also asked when authenticating after register has been done. Fixing that too.

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

Successfully merging a pull request may close this issue.

3 participants