Closed zacknewman closed 4 weeks ago
authenticatorDisplayName is likely going to be removed from the spec. But if it stays, this is valid.
authenticatorDisplayName is likely going to be removed from the spec. But if it stays, this is valid.
Really? #2151 was just opened yesterday.
Even though credentialRecord/authenticatorDisplayName
was added in #1880 along with credProps.authenticatorDisplayName
, we should still recommend RPs to provide some way for users to set a "nickname" for their credentials, even if credProps.authenticatorDisplayName
is deleted. So I think this is valid regardless of the outcome of that discussion.
Really? #2151 was just opened yesterday.
Yes, the sentiment in favour of dropping credProps.authenticatorDisplayName
came up in discussions at TPAC shortly after #2151 was opened.
1880 added the optional item
authenticatorDisplayName
to Credential Record; however it was not added to Step 27 of the registration ceremony nor Step 23 of the authentication ceremony. Seeing howattestationObject
andattestationClientDataJSON
exist in Step 27, it would be nice to also addauthenticatorDisplayName
. Honestly, I was under the impressionauthenticatorDisplayName
was only acredProps
thing; had it existed in the ceremony criteria section for data to store, I don't think I would have made that mistake.Something like below would be nice: