Test for system cert token loading after TPM ready
Add a browser test for the logic that triggers the system slot initialization whenever the TPM goes into the "ready" state as notified by cryptohomed (added in r698007). The test exercises the following codepath (this description skips some intermediate callers for the sake of brevity): 1. SystemTokenCertDBInitializer is notified by the chromeos::[Fake]CryptohomeClient that TpmInitStatusUpdated with |ready|==true; 2. chromeos::TPMTokenLoader::EnsureStarted() gets called; 3. crypto::InitializeTPMTokenAndSystemSlot() gets called. This is verified by the test by opening a web page in the Chrome OS Login screen that uses client cert authentication. If the codepath mentioned above wouldn't work, the test would fail due to ClientCertFilterChromeOS waiting infinitely for the result from crypto::GetSystemNSSKeySlot(). Bug: 725500 Change-Id: I17e0fa42d3fda7d0deed5f86a2ab99b079865b36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1815857 Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Reviewed-by:Matt Mueller <mattm@chromium.org> Reviewed-by:
David Benjamin <davidben@chromium.org> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Cr-Commit-Position: refs/heads/master@{#705243}
Showing
This diff is collapsed.
Please register or sign in to comment