New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 896045 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Participants' hotlists:
Better-Together-Launch-Blockers


Sign in to add a comment

Smart Lock signin attempts signin on every click

Project Member Reported by hansberry@chromium.org, Oct 16

Issue description

See b/117343194.

EasyUnlockService retries an auth attempt every time the user photo is clicked, messing up the first attempt. This breaks Smart Lock signin.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 16

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/faf0b7f8bab4d4b321646a98d32186db9d7a5479

commit faf0b7f8bab4d4b321646a98d32186db9d7a5479
Author: Ryan Hansberry <hansberry@chromium.org>
Date: Tue Oct 16 23:47:57 2018

Smart Lock: Do not start multiple auth attempts.

EasyUnlockService previously re-instantiated an EasyUnlockAuthAttempt
every time the user profile picture was tapped or clicked. This was
unnecessary, and caused situations where the account's cryptohome
could not be decrypted.

Bug:  896045 
Change-Id: I959ed3209caeb8d83519c8300d863a6288984740
Reviewed-on: https://chromium-review.googlesource.com/c/1285118
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#600190}
[modify] https://crrev.com/faf0b7f8bab4d4b321646a98d32186db9d7a5479/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service.cc

Labels: Merge-Request-71
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 18

Labels: -Merge-Request-71 Hotlist-Merge-Approved Merge-Approved-71
Your change meets the bar and is auto-approved for M71. Please go ahead and merge the CL to branch 3578 manually. Please contact milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Fixed (was: Started)
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 18

Labels: -merge-approved-71 merge-merged-3578
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/566fe5230cd0cbaef31ff92573ea439aded41055

commit 566fe5230cd0cbaef31ff92573ea439aded41055
Author: Kyle Horimoto <khorimoto@google.com>
Date: Thu Oct 18 00:45:46 2018

Smart Lock: Do not start multiple auth attempts.

EasyUnlockService previously re-instantiated an EasyUnlockAuthAttempt
every time the user profile picture was tapped or clicked. This was
unnecessary, and caused situations where the account's cryptohome
could not be decrypted.

TBR=hansberry@chromium.org

(cherry picked from commit faf0b7f8bab4d4b321646a98d32186db9d7a5479)

Bug:  896045 
Change-Id: I959ed3209caeb8d83519c8300d863a6288984740
Reviewed-on: https://chromium-review.googlesource.com/c/1285118
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#600190}
Reviewed-on: https://chromium-review.googlesource.com/c/1287629
Cr-Commit-Position: refs/branch-heads/3578@{#111}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
[modify] https://crrev.com/566fe5230cd0cbaef31ff92573ea439aded41055/chrome/browser/chromeos/login/easy_unlock/easy_unlock_service.cc

Labels: Merge-Merged-71-3578
The following revision refers to this bug: 
https://chromium.googlesource.com/chromium/src.git/+/566fe5230cd0cbaef31ff92573ea439aded41055

Commit: 566fe5230cd0cbaef31ff92573ea439aded41055
Author: khorimoto@google.com
Commiter: khorimoto@chromium.org
Date: 2018-10-18 00:45:46 +0000 UTC

Smart Lock: Do not start multiple auth attempts.

EasyUnlockService previously re-instantiated an EasyUnlockAuthAttempt
every time the user profile picture was tapped or clicked. This was
unnecessary, and caused situations where the account's cryptohome
could not be decrypted.

TBR=hansberry@chromium.org

(cherry picked from commit faf0b7f8bab4d4b321646a98d32186db9d7a5479)

Bug:  896045 
Change-Id: I959ed3209caeb8d83519c8300d863a6288984740
Reviewed-on: https://chromium-review.googlesource.com/c/1285118
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#600190}
Reviewed-on: https://chromium-review.googlesource.com/c/1287629
Cr-Commit-Position: refs/branch-heads/3578@{#111}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}

Sign in to add a comment