New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 660095 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 660109



Sign in to add a comment

Swarming new UI: sign in does not work on local deve server

Project Member Reported by no...@chromium.org, Oct 27 2016

Issue description

What steps will reproduce the problem?
(1) $ cd appengine/swarming
(2) $ ./tools/gae dev
(3) open http://localhost:8080
(4) Click "Sign in"

What is the expected output?
UI opens sign in view

What do you see instead?
Nothing changes


 

Comment 1 by mar...@chromium.org, Oct 27 2016

Cc: vadimsh@chromium.org aludwin@google.com
+Adrian as he may be surprised by this. Vadim for general authentication eliteness.
It probably doesn't know how to handle the absence of a client ID (that we provide via configs in real deployments, e.g. https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/settings.cfg#11).

I guess we can create and hardcode a development client ID with http://localhost:8080 redirect URL?..

Similarly, other (unconfigured) instances of Swarming server are probably broken too (now or after they are updated).

Comment 3 by kjlubick@google.com, Oct 27 2016

We already have one of those.  https://pantheon.corp.google.com/apis/credentials?project=chromium-swarm-dev the web oauth for /newui/* is configured for localhost:8080 and localhost:9050

Comment 4 by no...@chromium.org, Oct 27 2016

workaround:

echo 'ui_client_id: "20770472288-t5smpbpjptka4nd888fv0ctd23ftba2o.apps.googleusercontent.com' > appengine/swarming/configs/services/swarmingserver/CONFIGS/settings.cfg

Comment 5 by no...@chromium.org, Oct 27 2016

oops forgot a quote in the end of the file contents

Comment 6 by kjlubick@google.com, Oct 27 2016

Blocking: 660109

Comment 7 by kjlubick@google.com, Nov 16 2016

Status: Fixed (was: Assigned)
I think the workaround suggested by nodir is a reasonable longish term solution to this problem.

Sign in to add a comment