Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Component/s: None
-
Labels:None
Description
To better integrate some GEs we need to improve the management of the roles in the IDM. This is basically associating a (optional) JSON file to reach user/role. When the info of the "/USER" we get back the role info (as we do now) and also the included JSON.
Requirements:
*Allow the inclusion of a String/JSON (scope) associated to each ROLE. It has to be stores in the ROLE data model.
*Each new USER with a ROLE will be associated to the "Scope" of the ROLE in the USER data model (related to (1))
*When querying the user info, (/USER) such "Scope" should be included
Note that the Scope associated to a ROL must be seen as a template to fill in the SCOPE associated to the user. In other words, each user must have his own scope in the data model.
Extra functionality that we will need: an administrator must be able to modify the "Scope" of a given user that was created in the past. By default, the "scope" is the same that is associated to his role. This must be done by adding/removing whatever is needed. This enables fine grain fine tuning of the catalogue of actions available to a concrete user.
Also, we need this:
(1) We must allow an administrador to modify the "Scope" of a Role. This must be done selecting one of these options: "Overwirte the Scope of all the users associated to this role", or alternatively "Use new Scope just for New Users"
Issue Links
- relates to
-
TBP-16 Functional expansion of role management with JSON
- Closed
Activity
- All
- Comments
- History
- Activity
- Transitions
Finally this is not a requirement.