Closed Bug 1218517 Opened 10 years ago Closed 10 years ago

limit `crater` scopes

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

References

Details

The crater clientid (GZpee) has scope `*` which is way too broad! Brian, I can figure out what kinds of access you need if you let me know what sorts of API calls the tests are making.
Flags: needinfo?(banderson)
OK, I made the following change to the scopes: --- client-id:GZpee0SDRHm9fhYbaqKtuQ.old +++ client-id:GZpee0SDRHm9fhYbaqKtuQ.new @@ -1 +1,2 @@ -* +queue:create-task:aws-provisioner-v1/cratertest +queue:route:crater.* based on a look at the source -- the task seems to only use a single workerType, and the given route. It doesn't use task graphs, so no scheduler scopes. And it doesn't use any docker-worker features, so no need for any docker-worker scopes. :brson, please re-open if your crater tasks stop working -- otherwise, I'm considering this fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Flags: needinfo?(banderson)
Component: Authentication → Services
You need to log in before you can comment on or make changes to this bug.