signon_realm for HTTPS credentials which migrated from HTTP credentials was computed wrong first time by HttpPasswordStoreMigrator and it contained the whole URL path, while it should only contain the web origin. Because the signon realm is used to construct the SQL query that returns the forms that match a specific form, credentials which will be used for filling, the credentials with wrong signon_realm are never filled (because they don’t match).

https://crrev.com/c/1098967 solved this problem for future migrations, but because the wrong migrating code already ran, PasswordStore contains some credentials that were created during the migration to HTTPS and have wrong signon_realm.




 

signon_realm for HTTPS credentials which migrated from HTTP credentials was computed wrong first time by HttpPasswordStoreMigrator and it contained the whole URL path, while it should only contain the web origin. Because the signon realm is used to construct the SQL query that returns the forms that match a specific form, credentials which will be used for filling, the credentials with wrong signon_realm are never filled (because they don’t match).

https://crrev.com/c/1098967 solved this problem for future migrations, but because the wrong migrating code already ran, PasswordStore contains some credentials that were created during the migration to HTTPS and have wrong signon_realm.


See https://docs.google.com/document/d/139w-K9cuCzFaqANNiEixpGLojZ2Fc6wo_q2PXgk238A/edit?usp=sharing for more details.