Provide use case level authorization in addition to the existing user level authorization

The idea is a use case related authorization to provide a more fine granular means than the current user based authorization. What we are looking for is that for each user the Active Directory will maintain a list of use cases the users are allowed to work on. Before the users log on to CP4D they decide to work on which use case they want to work on. He approves the use in an company own rights management system which shares the information in an extra LDAP field. They should then only be authorized to work with the resources authorized for this use case.

Effectively this would be an authorization scenario. The goal is to use additional fields in the Active Directory, where the use cases are specified and based on this information access to certain resources the user has access to will be granted/denied.
So consequently this will have to be configured on resources within Cloud Pak for Data.

Example: User A is allowed to work with Catalog X but also with Catalog Y. However they also want to specify that Catalog X should only be worked with for Use Case 1 and Catalog Y for Use Case 2. When the user logs on they decide on the use case they want to work on and have only access to the so specified resources.
A use case could be self service analytics for health in-patient care or self service analytics for out-patient care. If they log on to the in-patient care use case, they want to only see the resources dedicated to in-patient care, not the out-patient care resources in order to prevent unwanted changes or usage from happening.

The key here is that it is the same person that can work on either of both use cases, but the concerns are kept as separated as possible in order to prevent accidental misuse of the wrong data assets or governance artifacts.
The Active Directory would provide the information about the use case and CP4D would have to map that to access rights.

Maybe this feature can be selectively enabled/disabled through the LDAP configuration page