coordination #6558
closed[epic] add/edit/remove users
100%
Description
Updated by okurz almost 9 years ago
- Category set to 130
- Priority changed from Normal to Low
Updated by coolo almost 7 years ago
- Target version set to future
I rather have proper worker permissions - and not hijack users.
Updated by okurz almost 5 years ago
- 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
Updated by okurz almost 5 years ago
- Related to action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication) added
Updated by okurz almost 5 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by ilausuch over 4 years ago
- Status changed from Workable to In Progress
Updated by ilausuch over 4 years ago
Updated by okurz over 4 years ago
- 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
Updated by okurz over 4 years ago
- 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"
Updated by okurz over 4 years ago
- Due date set to 2020-07-07
due to changes in a related task: #68705
Updated by okurz over 4 years ago
- 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.
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html