Closed Bug 1462459 Opened 7 years ago Closed 7 years ago

Missing scopes are reported incorrectly

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: impossibus, Unassigned)

Details

In the Client Manager, when I try to update the scopes of one of my existing clients I get an error that states I am missing scopes. However, I do actually have the required scopes -- it even says so in the error message. "You are missing scopes x, y. You have scopes x, y, z." (See below.) Credentials Manager also shows that I have the required scopes. So either I should be allowed to perform the action I'm requesting or the error message is inaccurate and I'm missing some other scopes. Error message ====== You do not have sufficient scopes. You are missing the following scopes: assume:moz-tree:level:1:gecko, assume:mozilla-group:active_scm_level_1 You have the scopes: [ "assume:everybody", "assume:hook-id:garbage/", "assume:hook-id:project-testpilot/", "assume:login-identity:mozilla-auth0/ad|Mozilla-LDAP|mfrydrychowicz", "assume:moz-tree:level:1:comm", "assume:moz-tree:level:1:gecko", "assume:mozilla-group:DevServicesWiki", "assume:mozilla-group:IntranetWiki", "assume:mozilla-group:StatsDashboard", "assume:mozilla-group:active_scm_level_1", "assume:mozilla-group:all_scm_level_1", "assume:mozilla-group:cloudservices_dev", "assume:mozilla-group:cloudservices_dev_ssh", "assume:mozilla-group:corp-vpn", "assume:mozilla-group:egencia_ca", "assume:mozilla-group:irccloud", ...]
It looks like you tried to add the single scope "assume:moz-tree:level:1:gecko, assume:mozilla-group:active_scm_level_1" rather than ["assume:moz-tree:level:1:gecko", "assume:mozilla-group:active_scm_level_1"]?
Oh, wow. Indeed. I have some suggestions for the Credentials Manager UI, then -- e.g. state that one scope per line is expected. :)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Or Client Manager, rather.
Component: Authentication → Services
You need to log in before you can comment on or make changes to this bug.