Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(817)

Unified Diff: blimp/docs/running.md

Issue 1958033003: Allows client to access auth token from command line specified file. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Adds documentation Created 4 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « blimp/common/switches.cc ('k') | blimp/engine/BUILD.gn » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: blimp/docs/running.md
diff --git a/blimp/docs/running.md b/blimp/docs/running.md
index 5d087f1a40d72113ba19ab9fa60fca24ef858524..17979b4fea3f7c68fd99469511e0a98f726a251e 100644
--- a/blimp/docs/running.md
+++ b/blimp/docs/running.md
@@ -23,6 +23,21 @@ file (e.g. `--engine-cert-path=/path/to/file.pem`.)
The engine sends partially rendered content to the client. To request the complete
page from the engine, use the `--download-whole-document` flag on the client.
+### Specifying the client auth token file
+The client needs access to a file containing a client auth token. One should
+make sure this file is available by pushing it onto the device before running
+the client. One can do this by running the following command:
+
+```bash
+adb push /path/to/blimp_client_token \
+ /data/data/org.chromium.blimp/blimp_client_token
+```
+
+To have the client use the given client auth token file, use the
+`--blimp-client-token-path` flag (e.g.
+`--blimp-client-token-path=/data/data/org.chromium.blimp/blimp_client_token`)
+
+
### Android Client
Install the Blimp APK with the following:
@@ -99,26 +114,3 @@ also start a new shell and keep the following command running:
Typically this would be `out-linux/Debug/gen/third_party/blimp_fonts`.
* `--disable-remote-fonts`: Disables downloading of custom web fonts in the
renderer.
-
-#### Typical invocation
-When the client connects to a manually specified engine instead of using the
-assigner, it will use a dummy token. The engine needs to know what this token
-is, so it must be provided using the `--blimp-client-token-path` flag. The token
-is available in the constant `kDummyClientToken` in
-`blimp/client/session/assignment_source.h`. You can easily store that to a file
-by running the following command once:
-
-```bash
-awk '{if ( match($0, /^\s*const char kDummyClientToken.*/) ) { print substr($5, 2, length($5)-3);} }' \
- ./blimp/client/session/assignment_source.h > /tmp/blimpengine-token
-```
-
-Then start the engine using these flags:
-
-```bash
-out-linux/Debug/blimp_engine_app \
- --android-fonts-path=out-linux/Debug/gen/third_party/blimp_fonts \
- --blimp-client-token-path=/tmp/blimpengine-token \
- --enable-logging=stderr \
- --vmodule="blimp*=1"
-```
« no previous file with comments | « blimp/common/switches.cc ('k') | blimp/engine/BUILD.gn » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698