Ki-Eun Shin
Ki-Eun Shin
I think the best effort for the attachment (transport) at this moment is asking for the specific attachment when creating the call by showing different UXs depending on the attachment...
> As far as I know, there are no browsers that currently allow users to manage registrations. All the registrations remain forever. For this, in case of Chrome (maybe Edge...
@akshayku depending on the services, the name can be other attributes like phone number or even nickname such information can be altered. Unlike the traditional web services, such RPs (services)...
In case of the name for user, the user has the consent for the modification since such name changes are requested by the user. For the RP case, RP may...
I agree. For the fetching URL from the remote source (https) happens at the time of registration once and then such fetched icon is stored in the authenticator. See following...
This issue seems to be duplicated to #199.
The `user.id` is the value provided (and assigned) by RP. The way to generate such value is up to RPs. Some RPs just generate hash value of username of the...
@agl Probably, Conditional UI helps for the user to leverage local credential if exist. But, how can we distinguish that the credential is coming from the platform authenticator or from...
@Firstyear Yup. The transport might be the security properties for the certain RPs. But, I'm more concerning about the UX flow. In many situations, the metadata is unavailable. So' I...
One thing to note is that the authenticatorAttachment in the create() and get() response is **nullable**. Sometimes the RP might not get any value from the response. I don't know...