[Passwords] Require matching username for UsernameFirstFlow
This change modifies `IsPossibleUsernameValid` to require that the possible username is part of an already saved credential for the same site. This will be later extended to only require a match with a local username saved on any site. For robustness the username and the set of allowed usernames are canonicalized, that is case and email providers are irrelevant. The existing requirements to only be ASCII and to not contain whitespace are dropped. Bug: 959776, 1167042 Change-Id: Ic50c954ddd7a4fd969c56295825ae717c870b915 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627278 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:Maria Kazinova <kazinova@google.com> Cr-Commit-Position: refs/heads/master@{#844013}
Showing
Please register or sign in to comment