Fix filling wrong username with a normal entry that has a passkey.
There are two possible situations with entries that has a passkey:
1) Entry only has a passkey. Username is set to KPEX_PASSKEY_USERNAME.
2) Entry has normal credentials and KPEX_PASSKEY_USERNAME.
In the second situation the normal username needs to be returned if entry has a passkey but KPEX_PASSKEY_USERNAME differs. The KPEX_PASSKEY_USERNAME attribute will be still used during authentication normally. The username only matters how the credential is displayed in the extension side, and during the Access Confirm Dialog.
Fixes #10840.
Testing strategy
Manually.
Type of change
✅ Bug fix (non-breaking change that fixes an issue)
Fix filling wrong username with a normal entry that has a passkey. There are two possible situations with entries that has a passkey: 1) Entry only has a passkey. Username is set to
KPEX_PASSKEY_USERNAME
. 2) Entry has normal credentials andKPEX_PASSKEY_USERNAME
.In the second situation the normal username needs to be returned if entry has a passkey but
KPEX_PASSKEY_USERNAME
differs. TheKPEX_PASSKEY_USERNAME
attribute will be still used during authentication normally. The username only matters how the credential is displayed in the extension side, and during the Access Confirm Dialog.Fixes #10840.
Testing strategy
Manually.
Type of change