Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
TBD
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Template:
Description
The FOLIO web application in some places assumes that every user object has a matching permissions user object. For example, i you edit a user that has no permissions user and try to add a permission to them, it will give you an error. Please change this so that, permissions user objects are created as needed. I.e. adding a permission to a user using the UI should check to see if a permissions user object exists. If it doesn't, rather than throwing an exception, it should create one and add the permission to the permissions user. There may be other places in the FOLIO web application that may need to be changed to handle this as well. This is the only place where I've seen an issue though.
This will help with regard to the batch management of users. We have around 40,000 users, but, only a few hundred will have permissions. It will allow a loader application not to have to create a lot of permissions users that have no permissions. Also, it will decouple the users and permissions modules and make it easier for managing users without also having to manage permissions.
TestRail: Results
Attachments
Issue Links
- relates to
-
MODUSERS-217 Improve users bulk insert/update performance
-
- Open
-