Managing Database Account Privileges for Generic Visualization Business Areas
Your company can use the Generic Visualization adapter to integrate an external data visualization tool with Oracle Life Sciences Data Hub see the Oracle Life Sciences Data Hub Adapter Toolkit Guide.
After integration, Definers must create Generic Visualization Business Area instances to allow access to specified sets of data through the visualization tool.
Unlike other Business Areas, which are installed in their Work Area's schema, Oracle LSH installs each Generic Visualization Business Area instance in its own schema outside the Work Area schema. There are simplified security requirements for data in this schema.
Users can log in to the integrated visualization tool using an Oracle LSH database account. The system checks if there is an Oracle LSH user account linked to the database account. If there is a linked user account, the system uses it to determine the user's privileges. If there is no linked user account, the system uses the database account itself to determine the user's privileges.
The database account can have one or two privileges assigned:
- Read Data. This privilege allows the user to view data that was never blinded and dummy data in Table instances that are currently blinded. All database accounts that should have access to the Business Area instance data should have this privilege.
- Read Unblind. This privilege allows the user to view data that has been permanently unblinded.
If a user should be able to view currently blinded data, he or she must have an Oracle LSH user account with all the required Blind Break privileges and a linked database account.
You can grant (and revoke) Read Data and Read Unblind privileges to database accounts for specific Business Area instances. Oracle LSH audits all changes to these permissions.
Parent topic: Creating Database Accounts