tree 731205cfae93d12f0ffc052c1d906c3a83b449f4
parent e397319112877329681530cf2b381f160c6602d8
author Yicheng Li <yichengli@chromium.org> 1607551035 -0800
committer Commit Bot <commit-bot@chromium.org> 1607976795 +0000

u2fd: Start WebAuthn handler on policy status change

This should have been part of http://crrev/c/2572025. Since we now
initialize WebAuthn handler only if policy is ready, there's a case
(typically OOBE) where the device policy takes time to load, and u2fd
decides not to initialize WebAuthn since device policy is not ready.
This causes WebAuthn to not work right after OOBE.

The U2fHid service actually has a callback registered with Session
Manager that retries starting service on device policy state change.
So the right thing to do is to also try starting WebAuthn in that
callback.

BUG=b:175228002
TEST=Unenroll and go through OOBE, WebAuthn works.
TEST=Enable U2F and try the U2F API registration/auth on
     https://securitykeys.info/qa.html

Change-Id: I6d733d40f33dc3ed32f508c1e44a7d37bba74c6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2583130
Tested-by: Yicheng Li <yichengli@chromium.org>
Reviewed-by: Andrey Pronin <apronin@chromium.org>
Commit-Queue: Yicheng Li <yichengli@chromium.org>
(cherry picked from commit 53b0c73c9f16cff4e23deb39bc4e09d01030d7e3)
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2590488
Reviewed-by: Yicheng Li <yichengli@chromium.org>