Enhancement to OAC - We need OAC to support user and group filtering from within the admin console

sdairiki-Oracle

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of): OIT Enterprise Engineering, we manage many internal OAC pods for LOBs. We have 25+ pods that are associated to a single IDCS stripe. I have exchanged emails and slacks w. alan.w.lee@oracle.com and he advise I log an ER for this enhancement.

Description (Required):

We need the ability to restrict what users and groups an OAC serviceadministrator can or cannot see from the OAC admin console (specifically, Console --> Users and Roles). As you know, currently any OAC admin can see all users and groups in the entire IDCS by browsing Users and Roles.

Use Case and Business Need (Required):

Improved security

Enhancement Request / Service Request: Enhancement

BalaGuddeti-Oracle

It seems having secondary IDCS stripes should be a workaround for this problem.

Check the blog How to create OAC instances on OCI Native using multiple stripes or instances of IDCS

https://blogs.oracle.com/analytics/post/how-to-create-oac-instances-on-oci-native-using-multiple-stripes-or-instances-of-idcs

sdairiki-Oracle

@BalaGuddeti-Oracle Having a 2nd stripe is not a viable work around. We have 25+ OAC pods. If each OAC had its own IDCS stripe, that would mitigate the issue, but that is not a scalable solution.