tree 0a5e2526e3fc7b9764704b3ff9f8f339015c8dc4
parent 5ee08616c7f55aac1088b1d59af8480c289f03e2
author Yicheng Li <yichengli@chromium.org> 1607551035 -0800
committer Commit Bot <commit-bot@chromium.org> 1607590842 +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>