Do not prompt and/or create copies when Android logins are filled into websites.

Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding websites and are used for a successful login, the user is prompted to save a new credential, and ultimately a copy of the credential, keyed by the web site, gets saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.  Later, these can lead to an out-of-date password stored for the Android app if the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new credentials, but simply update the usage count of the existing Android credential in-place while leaving the other meta-attributes untouched.

BUG=540609
TBR=vabr@chromium.org

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)

Committed: https://chromium.googlesource.com/chromium/src/+/8b349ff7c1b32ea1a71c15cd4abee11c4da46386

[engedy, 2016-01-12 19:16:35]

Description was changed from

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)
==========

to

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)
==========

[engedy, 2016-01-12 19:16:35]

engedy@chromium.org changed reviewers:
+ vabr@chromium.org

[engedy, 2016-01-12 19:17:37]

Description was changed from

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)
==========

to

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609
TBR=vabr@chromium.org

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)
==========

[engedy, 2016-01-12 19:33:39]

Description was changed from

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609
TBR=vabr@chromium.org

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)
==========

to

==========
Do not prompt and/or create copies when Android logins are filled into websites.

Presently, when logins from Android apps are filled into the corresponding
websites and are used for a successful login, the user is prompted to save a new
credential, and ultimately a copy of the credential, keyed by the web site, gets
saved to the password store.

This is a very confusing UX, and also results in duplicate logins being created.
 Later, these can lead to an out-of-date password stored for the Android app if
the Web password is ever updated in the future.

Instead, in this scenario, do not prompt at all, do not save any new
credentials, but simply update the usage count of the existing Android
credential in-place while leaving the other meta-attributes untouched.

BUG=540609
TBR=vabr@chromium.org

Review URL: https://codereview.chromium.org/1571813002

Cr-Commit-Position: refs/heads/master@{#368421}
(cherry picked from commit 90098fdb2f7fe52185ec1bce37252e89942712ad)

Committed:
https://chromium.googlesource.com/chromium/src/+/8b349ff7c1b32ea1a71c15cd4abe...
==========

[engedy, 2016-01-12 19:33:40]

Committed patchset #2 (id:20001) manually as
8b349ff7c1b32ea1a71c15cd4abee11c4da46386.