Pull the correct authentication token for the Blimp v0.6 client.
This involves the following things:
- When Blimp is turned on (or when the application starts with Blimp enabled), pull the authentication token from an account signed into Chrome and give it to the BlimpClientSession (being reworked into BlimpClientContext and tied into Chrome for Android in parallel). See TokenSourceImpl for how this is done in the Blimp v0.5 client. There is similar code already in Chrome. +nyquist@ for some advice on where this code is and how to access it.
- If no account is signed into Chrome, don't allow Blimp to be turned on and show a dialog directing the user to the sign in settings flow.
- If the account is deleted from Chrome's sync/sign in list, turn off Blimp automatically and show a dialog.
Note that this should all be bypassed if there is a custom engine ip/port specified in the command line.
Again this code should only run if built for the Blimp target.
Comment 1 by dtrainor@chromium.org
, Jul 25 2016Cc: -nyquist@chromium.org xingliu@chromium.org
Owner: nyquist@chromium.org