You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user MUST have some control over this behavior. As noted in §5.2 Requiring User Mediation, clearing cookies for an origin will also reset that origin’s prevent silent access flag the credential store to true. Additionally, the user agent SHOULD provide some UI affordance for disabling automatic sign-in for a particular origin. This could be tied to the notification that credentials have been provided to an origin, for example.
Current specs defines that control over user logout mediation is up to the relying party. If relying party enforce mediation through preventSilentAccess() then user will be forces to re-authenticate on next use. What if relying party, does not provide functionality to disable auto sign-in, and user agent does not have UI to enforce mediation(i.e. disable auto sign-in)? User will be forced to sign in every time he access the site, and his only option would be to remove credential entirely from storage to prevent that behavior.
This poses privacy and user experience issues, as user will be forced to login when he MAY not willing to do so, and it will be frustrating experience for him to manage such behavior.
User agents on their side can help to prevent both, by adding "auto sign-in" option, in auto sign-in prompt, and delaying auto sign-in by few second.
Based on my argument, I propose change "user agent SHOULD provide some UI affordance for disabling automatic sign-in for a particular origin." to "user agent MUST provide some UI affordance for disabling automatic sign-in for a particular origin."
The text was updated successfully, but these errors were encountered:
The user MUST have some control over this behavior. As noted in §5.2 Requiring User Mediation, clearing cookies for an origin will also reset that origin’s prevent silent access flag the credential store to true. The user agent MUST provide some UI affordance for disabling automatic sign-in for a particular origin. This could be tied to the notification that credentials have been provided to an origin, for example.
In section 6.6
Current specs defines that control over user logout mediation is up to the relying party. If relying party enforce mediation through
preventSilentAccess()
then user will be forces to re-authenticate on next use. What if relying party, does not provide functionality to disable auto sign-in, and user agent does not have UI to enforce mediation(i.e. disable auto sign-in)? User will be forced to sign in every time he access the site, and his only option would be to remove credential entirely from storage to prevent that behavior.This poses privacy and user experience issues, as user will be forced to login when he MAY not willing to do so, and it will be frustrating experience for him to manage such behavior.
User agents on their side can help to prevent both, by adding "auto sign-in" option, in auto sign-in prompt, and delaying auto sign-in by few second.
Based on my argument, I propose change "user agent
SHOULD
provide some UI affordance for disabling automatic sign-in for a particular origin." to "user agentMUST
provide some UI affordance for disabling automatic sign-in for a particular origin."The text was updated successfully, but these errors were encountered: