[FOLIO-906] Enable okapi internal module in most boxes Created: 24/Oct/17 Updated: 12/Nov/18 Resolved: 26/Oct/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Heikki Levanto | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint25 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 45 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Description |
|
Now that we have the Okapi management functions moved into the internal module, this module should be enabled for the tenants that get created. |
| Comments |
| Comment by Heikki Levanto [ 24/Oct/17 ] |
|
The module is called something like okapi-2.0.2. Enabling the module makes it possible for the UI to request lists of enabled modules etc, without any workarounds. It will not make it possible for them to change things in Okapi, unless they have the right permissions, which is not likely, since
|
| Comment by Jakub Skoczen [ 25/Oct/17 ] |
|
What about securing the super tenant with password when setting up the system? Is that done? |
| Comment by Wayne Schneider [ 26/Oct/17 ] |
|
Updated tenant-data role to enable internal module. |
| Comment by Heikki Levanto [ 27/Oct/17 ] |
|
@Jakub - That is
|