coordination #6558
closed
[epic] add/edit/remove users
Added by lnussel almost 10 years ago.
Updated over 4 years ago.
Category:
Feature requests
Estimated time:
(Total: 0.00 h)
Description
Acceptance criteria¶
- AC1: Admins can add/edit/remove users over the API and webUI
Suggestions¶
- add interface to add, edit and remove users
- also allow to edit api keys so one could create dedicated users for e.g. workers.
- Category set to 130
- Priority changed from Normal to Low
- Target version set to future
I rather have proper worker permissions - and not hijack users.
- Target version changed from future to future
- Category changed from 130 to Feature requests
- Related to action #47210: "Users" page in web UI resets to showing the first page of 10 users every time you make a change added
- Related to action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication) added
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Due date set to 2020-07-07
- Start date changed from 2015-03-05 to 2020-07-07
due to changes in a related task: #68702
- Subject changed from add/edit/remove users to [epic] add/edit/remove users
- Status changed from In Progress to Blocked
- Assignee set to okurz
We discussed in the retro and clarified that likely we have (at least) two requests mixed together here. One is "remove existing users", that should be easy to do and we can do first. The other would be to "add manual users that are not managed over external identify provider", e.g. dedicated "users" for workers, etc. Created specific subtask for "remove user"
- Due date set to 2020-07-07
due to changes in a related task: #68705
- Status changed from Blocked to Resolved
Support for removing users had been done, see subtasks. For the "add manual users that are not managed over external identify provider" as that was a single-line idea anyway I have added that in #65271#note-23 and right now do not see the priority for that as admins that create workers most likely have DB access anyway and we describe that approach in scripts and docs as well.
- Tracker changed from action to coordination
Also available in: Atom
PDF