Closed Bug 1533591 Opened 6 years ago Closed 6 years ago

adjust auth API to issue websocktunnel tokens with audience

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

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.

Flags: needinfo?(16103127vaibhav)

I will be happy to work on it & start working on it right away.

Flags: needinfo?(16103127vaibhav)

I'm going to try to work on this this week; if not, please take it back next weekend :D

Assignee: nobody → dustin

deployed to production!

Ah, I had forgotten to rename the WEBHOOKTUNNEL_SECRET to WEBSOCKTUNNEL_SECRET in Heroku.

It was a big task indeed, I would have taken more a week for sure.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED

Oh, I still need to deploy this with terraform.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: