As already discussed here there’s a need for users to have more than 5 physical keys added to their account. That previous topic was about supporting more than 5 keys for 2FA, this one is, as discussed in the previous topic, specifically about increasing that limit for passwordless login too.
This FR is to increase the number of passkeys that can be added. My suggestion would be at least 8 but more is probably better in this case.
Description:
While there is a limit of 10 passkeys to be used as a 2nd factor, currently, the system limits the number of usable passkeys to 5 per account to logon and decrypt.
While this may cover basic use cases, it is insufficient for power users and professional environments that rely on a mix of ecosystem-based and physical security keys.
The Problem:
A standard modern setup quickly exhausts the current limit:
3 Platform Keys: Syncing across primary ecosystems (e.g., iCloud Keychain for iOS, Google Password Manager for Android, and Windows Hello).
2 Backup Keys: Standard security best practice involves at least two physical hardware keys kept in separate locations.
With 5 keys registered, the limit is reached. This leaves no room for additional (hardware) keys required for devices that do not support platform sync, such as Linux workstations or restricted corporate laptops.
Proposed Solution:
Increase the maximum number of allowed passkeys to 10 (or more) to be used for login and decryption. This would then match the number of keys currently usable as a 2nd factor.
Key Benefits:
Improved Accessibility: Users can authenticate on “non-standard” systems (Linux, work-managed devices) without deleting existing keys.
Enhanced Redundancy: Provides headroom for users to maintain multiple backup hardware keys.
Future-Proofing: Accounts for the growing trend of device-bound passkeys across various operating systems.