GitLab

This relands the test from the commit
8fd76b23 that
got reverted for the second time due to flakiness. The test is relanded
as DISABLED, in order to land all the lgtm'ed plumbing that would anyway
be necessary even after fixing all possible flakiness.

Original change's description:
> Add browser tests for smart card SAML login
>
> Provide test coverage for the scenario where a new user authenticates
> via SAML using a smart card (or, generally speaking, using a security
> token via an extension using the chrome.certificateProvider API).
>
> This also provides some test coverage for the <security-token-pin>
> Polymer element used on the Login Screen.
>
> Bug: 1033936
> Change-Id: I5ded32e0570eb7227c77b954c33d12c1a8a62914
> Reviewed-on:
https://chromium-review.googlesource.com/c/chromium/src/+/1968989
> Reviewed-by: Alexander Alekseev <alemate@chromium.org>
> Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
> Reviewed-by: Alexander Hendrich <hendrich@chromium.org>
> Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#734510}

Bug: 1033936
Tbr: alemate@chromium.org, hendrich@chromium.org
Test: run the test locally with is_chrome_branded=true
Change-Id: Ie3431acfdb589bd7d9ed443d283de996af18a266
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032116
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#738234}