Open
Bug 1408457
Opened 8 years ago
Updated 4 years ago
When doing a task that communicates with TaskCluster, should verify scopes are not expired
Categories
(Tree Management :: Treeherder, enhancement, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
NEW
People
(Reporter: camd, Unassigned)
Details
In some actions like adding new jobs, we only check our internal $scope.user.loggedin to determine if the user is logged in and can, therefore, trigger new jobs. However, the expiration in TaskCluster may be different than ours if the tab's been open for a few days.
We should make a call to auth.currentScopes to verify that the scopes the user has are still current before making the call. Otherwise, they may have tabbed away only to come back hours later, chagrined, to realize it failed due to expired scopes.
https://docs.taskcluster.net/reference/platform/taskcluster-auth/references/api#currentScopes
| Reporter | ||
Updated•8 years ago
|
Priority: -- → P1
| Reporter | ||
Updated•8 years ago
|
Assignee: nobody → cdawson
Updated•8 years ago
|
Component: Treeherder → Treeherder: Frontend
Updated•7 years ago
|
Component: Treeherder: Frontend → Treeherder: Job Triggering & Cancellation
| Reporter | ||
Comment 1•6 years ago
|
||
I'm not going to get to this any time soon and I don't think it's super critical. But still worth doing at some point.
Assignee: cdawson → nobody
Priority: P1 → P3
| Assignee | ||
Updated•4 years ago
|
Component: Treeherder: Job Triggering & Cancellation → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•