Add an new error case

Jérémy JAMET
2025-10-22 22:32:59 +02:00
parent 4efbbb3a32
commit bc9ab37e32

@@ -191,12 +191,21 @@ In order to meet minimum security requirements, KeePassDX verifies that a passke
## Server rejection
In some cases, the server will reject the Passkey you are trying to use for authentication. This happens if you used **another Passkey client to create your keys** but the [Backup Eligibility](#Backup-Eligibility) variable was disabled.
In some cases, the server will reject the Passkey you are trying to use for authentication.
This can happen if you used **another Passkey client to create your keys** but the [Backup Eligibility](#Backup-Eligibility) variable was disabled, or if you saved the browser package directly to the entry.
There are two solutions in this case:
### Passkey created externally
If the passkey has been saved by another client or on another device with BE disabled, there are two solutions:
- **Simply create a new Passkey entry for this service**. This is the recommended method.
- Add the protected custom field `KPEX_PASSKEY_FLAG_BE` with a value of `0` to the Passkey entry if the field label `Passkey Backup Eligibility` is not present. **This solution is not recommended**, as it manually changes a value on the assumption that the server will accept a backup (i.e., the use of a passkey on another client) simply because the variable has the same value but does not actually verify the client used.
### Bad signature
If you have registered your browser signature in the entry:
- Enable the browser in the list of privileged apps
- Remove the `AndroidApp` and `AndroidApp Signature` fields in the entry
## Out of time
`Out of time` simply indicates that the time for creating or using the Passkey has expired. You must therefore repeat the procedure by closing and reopening the dialog box.