Luigi Semenzato
2018-12-06 23:42:17 UTC
Hi,
I am writing some Chrome OS automated test that requires loading
several large Google sites (gmail, docs, etc.) I want to use WPR
(wprgo) for stability. I am stumbling on authentication.
There are two approaches. One is to log on to the chromebook (via
webui javascript, we do this already for a test account using
oobe.loginForTest()), and then we are automatically signed in with
Gaia. The problem with this approach is that it (possibly) requires
starting chrome with --disable-gaia-services, which prevents the
creation of required authentication tokens. (I have tried removing
that flag and hit problems that I haven't debugged yet.)
The second is to log on as the test user, or as the guest user, and
then log on to Google via the browser. This also doesn't work with
WPR: the URLs used in the process are generated dynamically and
contain a time stamp (and a hash, which might depend on the time
stamp). I don't know how easy it would be to work around this. I can
maybe change wprgo to match URLs after removing hashes and timestamps,
but if the served content of those URLs also contains hashes or
timestamps, this won't go very far.
I am wondering if anybody who has experience with this can make
suggestions on how to proceed.
Thanks!
I am writing some Chrome OS automated test that requires loading
several large Google sites (gmail, docs, etc.) I want to use WPR
(wprgo) for stability. I am stumbling on authentication.
There are two approaches. One is to log on to the chromebook (via
webui javascript, we do this already for a test account using
oobe.loginForTest()), and then we are automatically signed in with
Gaia. The problem with this approach is that it (possibly) requires
starting chrome with --disable-gaia-services, which prevents the
creation of required authentication tokens. (I have tried removing
that flag and hit problems that I haven't debugged yet.)
The second is to log on as the test user, or as the guest user, and
then log on to Google via the browser. This also doesn't work with
WPR: the URLs used in the process are generated dynamically and
contain a time stamp (and a hash, which might depend on the time
stamp). I don't know how easy it would be to work around this. I can
maybe change wprgo to match URLs after removing hashes and timestamps,
but if the served content of those URLs also contains hashes or
timestamps, this won't go very far.
I am wondering if anybody who has experience with this can make
suggestions on how to proceed.
Thanks!
--
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAA25o9Q6F00-yWhKi-wzU5Tbv7-3u73Ot%2BbLpTF1a0Esv56xKA%40mail.gmail.com.
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAA25o9Q6F00-yWhKi-wzU5Tbv7-3u73Ot%2BbLpTF1a0Esv56xKA%40mail.gmail.com.