Hello,
It seems to me showing the creation date of a passkey (which cannot be cloned) is kinda useless. It would be better to show the public key or a hash so users can compare them and now if they are the same or not because the creation date does not give a lot of infos.
Thanks.
@DorianCoding Welcome to the forum!
I guess that’s at least debatable. – For keeping a record of things, the creation date is not totally useless. (and e.g. knowing “creation date of passwords” is not the smallest feature request here, e.g. for expiration dates and “age reports”).
As far as I know, the public key doesn’t even get stored in Bitwarden. (i.e. not stored in the authenticator in general)
And what hash do you mean? (I’m not sure, hashing is even involved in the passkey registration and authentication ceremonies…)
Here in this post by @kpiris you can see how a passkey looks like in the Bitwarden data - and what get’s stored.
For most end-users (including me) almost everything you can see there wouldn’t be useful to see in the passkey field in the login item, I guess… [PS: Addition after @DorianCoding’s response: okay, maybe userName, userDisplayName or rpName (rp = relying part, i.e. the corresponding website) could be good to be able to see]
If we had the possibility to store multiple passkeys in one login item - let’s say at least two - I can imagine, it would be useful to be able to see which of the two “passkeys” would be the discoverable credential (= passkey in the strict definition) and which of the two would be the non-discoverable credential (= not a passkey in the strict definition). Because if you had to choose the credential for authentication, you had to choose the right one. (and even for registration, it would be nice to see, which kind of credential is already registered and which is “missing”…)
For the whole item, sure but for passkeys, how to make a difference between if you have many?
The public key or a hash (like SHA256) of a key could be computed. Or in a nutshell, whatever is used, something that someone can use to identify if one key is the same as another (or even the user display) because they cannot be cloned for instance.
userDisplayName and username would be useful to separate different keys and a human-readable form of all this (without the private key for safety) to compare keys (or just a button on Bitwarden to compare in the background).
You’re right, userName and userDisplayName could be useful! I added that in my previous post.
So, but, as long as only one passkey can be stored in a login item, it must not be differentiated, I guess, as the name/title of the login item should make sure where the passkey belongs to. (if we had the option to store multiple passkey in one login item, as written before, they would have to be differentiated from each other)
I still don’t get, why you want to “compare” something?? Could you elaborate a bit, why that would be necessary or useful for you?
If I have one passkey that might be able to be clone in the future or imported in a vault for instance, I could check there are the same.