[FOLIO-3394] Make diku_admin user uneditable via UI in reference builds Created: 19/Jan/22 Updated: 01/Dec/22 Resolved: 18/Feb/22 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | DevOps Sprint 133 | ||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||
| Front End Estimator: | John Malconian | ||||||||||||
| Description |
|
Zak Burke has implemented an optional feature in the ui-users app which could make specified users uneditable via the app. Details are here - https://folio-org.atlassian.net/browse/UIU-2499. The best use case for this feature is probably the diku_admin user in FOLIO reference builds. Should be an optional step added to existing folio-ansible role. |
| Comments |
| Comment by John Malconian [ 18/Feb/22 ] |
|
This feature has been implemented as an optional component in the post-config-entries role of folio-ansible. Currently enabled for the diku_admin user on hosted folio-snapshot builds. |