[FOLIO-595] Superuser Created: 09/May/17 Updated: 12/Apr/23 Resolved: 12/Apr/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Heikki Levanto | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | dublin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
Do we need a root-like superuser, who will automatically have all possible permissions? And/or some template for creating new users? |
| Comments |
| Comment by Heikki Levanto [ 09/May/17 ] |
|
As we get more and more modules, and each come with more and more permissions, maintaining a hard-coded "diku-admin" gets tedious. On many systems there exists a superuser (like "root" in Unix), that can automatically do everything. Such a thing might come in handy here too. On the other hand, the system is probably safer without such thing. Also, creating new users becomes tedious, with this ever-increasing list of permissions. Maybe it would be useful to create a template-user, and copy its permissions over to a newly created user. Or just copy some existing user to begin with? Stuff to discuss in Dublin |
| Comment by Erin Nettifee [ 12/Apr/23 ] |
|
This is four years old; if the configuration needs to happen, a new ticket can be opened. |