Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

I want to restrict user to access only schema related to that user in BIP Model

Received Response
271
Views
4
Comments
Rank 5 - Community Champion

Hello All,

I created one SQL query based data model in BI publisher using one JDBC connection with a data base user , let's say XYZ.

I want to restrict user to access only schema related to that user, i.e. XYZ.

However it is able to access all other schema as per below screen shot:

pastedImage_0.png

Is there a way to restrict this user to access objects for other schema. In drop down list , all users/schema are getting listed and all db objects pertaining to those schema.

Thanks,

Rajneesh

Welcome!

It looks like you're new here. Sign in or register to get started.

Answers

  • Rank 2 - Community Beginner

    What's listed is what the user (utilized in the JDBC to open the connection) has access to in the DB. You can't restrict in BIP if the user has a larger perimeter in the DB. So the answer lies in the DB, not BIP.

  • Rank 5 - Community Champion

    I tried to restrict the access in the DB, so now data set user can not access the data of other schema.

    However other schemas are still getting listed. One can see what all schemas are available within the database.

    Thanks,

    Rajneesh

  • Rank 2 - Community Beginner

    A pity.

    But also in order to stick to forum rules I have to ask you to delete the MOS content as it's forbidden to be posted out onto a public forum.

  • Rank 5 - Community Champion

    Hello All,

    I got the solution and sharing here so that it may be useful for others with similar problem in future:

    Create below view on JDBC user schema

           create or replace view all_users  

        as select * from sys.all_users 

        where username = sys_context('userenv','current_user'); 

    OBIEE/OAS's BIP  is querying table all_users which is having public grant.

    If we create a view with same user and that list only current_user then this issue solved.

    I tested it and worked perfectly fine.

    Thanks,

    Rajneesh

Welcome!

It looks like you're new here. Sign in or register to get started.