Open Bug 1630651 Opened 4 years ago Updated 2 years ago

Provide a way for non-browser clients to get an authenticated connection

Categories

(Cloud Services :: Server: Remote Settings, task, P2)

task

Tracking

(Not tracked)

People

(Reporter: standard8, Assigned: leplatrem)

Details

With the search-config bucket on remote settings, we're typically using an upload script quite frequently to upload a configuration.

Currently we have to sign into staging or prod, and manually copy the authentication header to the script.

It would be nicer if we could do this automatically. Taskcluster have scripts that you can run from the command line which will open up the browser, let you sign in, then return the authentication token to the command line app.

I don't know if this just needs changes to our scripts, or if we need server side changes as well.

Taskcluster have scripts that you can run from the command line which will open up the browser, let you sign in, then return the authentication token to the command line app.

https://github.com/taskcluster/taskcluster/blob/2a78f720df5dc0eaf5f195f1ec1ef7959cb68fbf/clients/client-shell/cmds/signin/signin.go

Apparently it just consists in spawning a local HTTP server and a browser at http://localhost that will go through the OAuth dance.
If I remember correctly, localhost should be among the allowed hosts for the OAuth dance on Remote Settings, so we should be able to do the mimic TaskCluster signin CLI tool.

Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.