adjust auth API to issue websocktunnel tokens with audience
Categories
(Taskcluster :: Services, enhancement)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: dustin)
References
Details
Attachments
(1 file)
https://docs.taskcluster.net/docs/reference/platform/taskcluster-auth/references/api#websocktunnelToken
doesn't include anything about audiences, as added in bug 1517015.
Let's add wstAudience and wstClient params to that API method, and use "auth:websockproxy:<wstAudience>/<wstClient>" as the scope. So no more generation of a random tunnelId using slugid.
Vaibhav, is this something you'd be interested in working on? Time is a little critical -- ideally it'd be finished in a week or so. If that's too soon, I'm also happy to take care of this.
Comment 1•6 years ago
|
||
I will be happy to work on it & start working on it right away.
| Assignee | ||
Comment 2•6 years ago
|
||
I'm going to try to work on this this week; if not, please take it back next weekend :D
| Assignee | ||
Comment 3•6 years ago
|
||
https://github.com/taskcluster/taskcluster/pull/437
Sorry Vaibhav! :)
| Assignee | ||
Comment 4•6 years ago
|
||
deployed to production!
| Assignee | ||
Comment 5•6 years ago
|
||
| Assignee | ||
Comment 6•6 years ago
|
||
Ah, I had forgotten to rename the WEBHOOKTUNNEL_SECRET to WEBSOCKTUNNEL_SECRET in Heroku.
Comment 7•6 years ago
|
||
It was a big task indeed, I would have taken more a week for sure.
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 8•6 years ago
|
||
Oh, I still need to deploy this with terraform.
| Assignee | ||
Comment 9•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Description
•