[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:
Relates
relates to FOLIO-756 Secure folio-registry Closed
relates to OKAPI-388 Preload permission(set)s when enablin... Closed
relates to STCOR-69 /about should report on enabled modul... Closed
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 OKAPI-388 Closed prevents those permissions from being loaded in mod-perms, for now.

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 FOLIO-913 Closed . I am working on it, but running into Postgres problems

Generated at Thu Feb 08 23:09:12 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.