GitLab

Pipe the authenticating user's AccountId down to the UI-related code
that shows security token PIN dialogs, so that the UI layer has ability
to correctly tie the PIN UI with the needed user.

Before this CL, the UI code has to assume that the currently selected
user is the one that for which the PIN request should be shown. However,
this assumption is unreliable in general: for example, the user could
have already clicked a different user pod before the PIN request
arrived, and as a result the PIN dialog would be shown on a wrong user
pod.

This CL extracts the AccountId based on the AccountIdentifier
information supplied by the cryptohomed to the
org.chromium.CryptohomeKeyDelegateInterface D-Bus service exposed by
the browser.

Bug: 983103
Change-Id: I55999c64f3c9af29fa8c231210ad3282643da885
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1742172
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Igor <igorcov@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#685548}