Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 43 Oracle Analytics and AI Sharing Center
- 19 Oracle Analytics and AI Lounge
- 283 Oracle Analytics and AI News
- 60 Oracle Analytics and AI Videos
- 16.3K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 108 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Access controls for Connections
Add access controls to Connections to limit who can use the Connection to create a dataset. Envision 3 options (1) Full Control which allows editing connection (2) Allow, which would allow the user to create a dataset using the connection (would likely also need Author role) and (3) Disallow, would prevent the user from creating a dataset using Connection.
Use case. Connection created to the primary database to replicate Classic DDR reports. Current functionality allows any Author to create a dataset if they know the DB table name (can be found in the SQL in the DV Developer reporting). Need to limit which DB tables Authors can use, as datasets bypass row-level security in RPD for confidential data.
Comments
-
You can control re-use of an exist connection by changing the Access settings on a connection. If you remove all access from a user or group -- they will not be able to create a dataset from the connection.
We will need an improvement to control whether a Content Author can create a new connection, or it is not allowed. Today, Content Authors can add connections.
0
