Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 41 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 277 Oracle Analytics and AI News
- 50 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Idea Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 18 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Access to tables
I want to give access on table level to developers as want to restrict the sensitive or salary related data
Also they should not be able to see the data in table even in Data model using select query
Eg: select * from "Salary_tb"
Answers
-
Hi Anuksha
Please review the given documentation link and use the secured tables
Doc ID 1537196.1 Fusion Apps - How Can A BI Publisher Report Based On A SQL Query Use The Security Roles In Fusion Applications?
0 -
Hi @AnushkaUrunkar,
Welcome to the Oracle Analytics Community!
It seems it is not possible to restrict BI Publisher Data Models to specific tables.
Please check the following Oracle Note:
Hope this help.
Thank you.
0 -
When we do untitled DM will this solution work for that as well?
0 -
Our problem is like live data is in PROD and we have dedicated team to support the PROD related issues.
Now we want to minimize the team work so that dev team can debug there issues on there own only they should not be able to access the PII data and salary related data.
0 -
Hi @AnushkaUrunkar,
Ideally you need to do the Data Masking in your non-prod environment so that developers will not be able to see the sensitive real data.
Here's a good read which can provide more information.
Hope this help.
Thank you.
0 -
But we have live data on PROD itself not always we can produce the issues on non-prod environment
0 -
It is not possible to restrict BI Publisher Data Models to specific tables.
Please check the following Oracle Note:
Here are some ideas in the idea lab requesting that feature. I'll recommend to go through those and upvote, comment so that Oracle might consider these in future release.
GSI - Data Source Access across Oracle Pillars (HCM and FIN) - BI Admin — Oracle Analytics
Restrict BIP access (table access) for person, sensitive data — Oracle Analytics
Hope this clarify.
Thank you.
0 -
Your problem isn't about restricting the tables or tables content somebody can access in a Publisher data model, because that can easily be managed with common database security (as you talk about tables I assume a database to be involved).
Your problem is more about Fusion not giving you the required granularity in the security for your needs.
If it's only about Fusion, then it isn't really a Publisher issue, it's an implementation choice of how Fusion decided to implement security and use various products, like Publisher. If this is the case, then you should try to discuss and report your issues in the forum covering Fusion products:
Publisher will just enforce whatever security is implemented based on the credentials used to connect to the source. If those credentials have access to too many tables or content, then Publisher can't do anything for it, also because it isn't its role: it does just respect whatever security has been used and whatever credential has been defined in Publisher.
0
