| Oracle® Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) E10541-01 |
|
 Previous |
 Next |
| Oracle® Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) E10541-01 |
|
Previous |
Next |
This appendix explains how to manage security for dashboards and analyses such that users have only:
Access to objects in the Oracle BI Presentation Catalog that are appropriate to them.
Access to features and tasks that are appropriate to them.
For detailed information about securing an Oracle Business Intelligence system, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
This appendix contains the following sections:
Section C.1, "Managing Security for Users of Oracle BI Presentation Services"
Section C.3, "Inheritance of Permissions and Privileges for Oracle BI Presentation Services"
System administrators must configure a business intelligence system to ensure that all functionality (including administrative functionality) is secured so that only authorized users can access the system to perform appropriate operations. Administrators also must be able to configure the system to secure all middle-tier communications.
This overview section contains the following topics:
Section C.1.1, "Where Are Oracle BI Presentation Services Security Settings Made?"
Section C.1.2, "What are the Security Goals in Oracle BI Presentation Services?"
Section C.1.3, "How Are Permissions and Privileges Assigned to Users?"
Security settings that affect users of Presentation Services are made in the following Oracle Business Intelligence components:
Oracle BI Administration Tool — Enables you to perform the following tasks:
Set permissions for business models, tables, columns, and subject areas.
Specify database access for each user.
Specify filters to limit the data accessible by users.
Set authentication options.
For information, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
Oracle BI Presentation Services Administration — Enables you to set privileges for users to access features and functions such as editing views and creating agents and prompts.
Oracle BI Presentation Services — Enables you to assign permissions for objects in the Oracle BI Presentation Catalog.
In previous releases, you could assign permissions to objects from the Presentation Services Administration pages. In this release, you set permissions either in the Catalog Manager or the Catalog page of Presentation Services. See Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition for information on assigning permissions in Presentation Services.
Catalog Manager — Enables you to set permissions for Oracle BI Presentation Catalog objects. For information on Catalog Manager, see Chapter 11, "Configuring Connections to External Systems."
When maintaining security in Presentation Services, you must ensure the following:
Only the appropriate users can sign in and access Presentation Services. You must assign sign-in rights and authenticate users through the Oracle BI Server.
Authentication is the process of using a user name and password to identify someone who is logging on. Authenticated users are then given appropriate authorization to access a system, in this case Presentation Services. Presentation Services does not have its own authentication system; it relies on the authentication system that it inherits from the Oracle BI Server.
All users who sign in to Presentation Services are granted the AuthenticatedUser role and any other roles that they were assigned in Fusion Middleware Control.
For information about authentication, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Users can access only the objects that are appropriate to them. You apply access control in the form of permissions, as described in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Users have the ability to access features and functions that are appropriate to them. You apply user rights in the form of privileges. Example privileges are "Edit systemwide column formats" and "Create agents."
Users are either granted or denied a specific privilege. These associations are created in a privilege assignment table, as described in Section C.2.3, "Managing Presentation Services Privileges."
You can configure Oracle Business Intelligence to use the single sign-on feature from the Web server. Presentation Services can use this feature when obtaining information for end users. For complete information on single sign-on, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
When you assign permissions and privileges in Presentation Services, you can assign them in one of the following ways:
To application roles — This is the recommended way of assigning permissions and privileges. Application roles provide much easier maintenance of users and their assignments. An application role defines a set of permissions granted to a user or group that has that role in the system's identity store. An application role is assigned in accordance with specific conditions. As such, application roles are granted dynamically based on the conditions present at the time authentication occurs.
See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information on application roles.
To individual users — You can assign permissions and privileges to specific users, but such assignments can be more difficult to maintain and so this approach is not recommended.
To Catalog groups — This approach is maintained for backward compatibility with previous releases only.
See Section C.2.2, "Working with Catalog Groups" for information on Catalog groups.
You can use the Administration pages in Oracle BI Presentation Services to perform the tasks that are described in the following sections:
The main Administration page contains links that allow you to display other administration pages for performing various functions, including those related to users in Presentation Services. You can obtain information about all these pages by clicking the Help button in the upper-right corner.
|
Note: Use care if multiple users have access to the Administration pages, because they can overwrite each other's changes. Suppose UserA and UserB are both accessing and modifying the Manage Privileges page. If UserA saves updates to privileges while UserB is also editing them, then UserB's changes are overwritten by those that UserA saved. |
In previous releases, Presentation Services groups were used for organizing users. Presentation Services group membership was used to determine the permissions and privileges that are associated with a user, either by explicit assignment or inheritance. In this release, Presentation Services groups have the following characteristics:
Are referred to as Catalog groups.
Can contain users, application roles, or other Catalog groups.
Exist only for the purposes of compatibility with previous releases and only with Presentation Services.
No longer have their own passwords.
While you can continue to use Catalog groups, it is recommended that you move to the use of application roles rather than Catalog groups for organizing users.
Presentation Services administrators must ensure that the names of Catalog groups are different from any user IDs that are used to log in to Oracle BI Presentation Services. If a user and a Catalog group share the same name, then the user receives an Invalid Account message when attempting to log in to Oracle BI Presentation Services.
On the Administration page in Presentation Services, you can perform the tasks that are described in the following sections:
To create Catalog groups:
From the Home page in Presentation Services, select Administration.
Click the Manage Catalog Groups link.
Click Create a New Catalog Group.
In the Add Group dialog, enter a name for the group.
Use the shuttle control to select the Catalog groups, users, and application roles to include in this group.
|
Tip: It is best practice to not include application roles in Catalog groups, to avoid complex group inheritance and maintenance situations. In particular do not add the AuthenticatedUser role to any other Catalog groups that you create. This ensures that only the desired Catalog groups (and users) have the specified permissions and privileges, by preventing users or authenticated users from unintentionally inheriting permissions and privileges from another Catalog group. |
Click OK.
From the Home page in Presentation Services, select Administration.
Click the Manage Catalog Groups link.
On the Manage Catalog Groups page, select the one or more groups to delete.
To help you locate the group that you want, enter text in the Name field and click Search.
Click Delete Selected Groups.
Click OK to confirm the deletion.
From the Home page in Presentation Services, select Administration.
Click the Manage Catalog Groups link.
On the Manage Catalog Groups page, select the group to edit.
To help you locate the group that you want, enter text in the Name field and click Search.
You can click the More Groups button to display the next 25 groups in the list.
In the Edit Group dialog, change the name or add or remove application roles, Catalog groups, and users.
Click OK.
This section contains the following topics about privileges in Presentation Services:
Section C.2.3.2, "Setting Privileges in Oracle BI Presentation Services Administration."
Section C.2.3.3, "Default Oracle BI Presentation Services Privilege Assignments."
Privileges control the rights that users have to access the features and functionality of Oracle BI Presentation Services. Privileges are granted or denied to specific application roles, individual users, and Catalog groups using a privilege assignment table.
Like permissions, privileges are either explicitly set or are inherited through role or group membership. Explicitly denying a privilege takes precedence over any granted, inherited privilege. For example, if a user is explicitly denied access to the privilege to edit column formulas, but is a member of an application role that has inherited the privilege, then the user cannot edit column formulas.
Privileges are most commonly granted to the BIAuthor or BIConsumer roles. This allows users access to common features and functions of Presentation Services. While you can continue to grant privileges to Catalog groups, it is recommended that you switch the grants to application roles.
On the Manage Privileges Administration page in Presentation Services, you can view and administer privileges for application roles, individual users, and Catalog groups.
From the Home page in Presentation Services, select Administration.
Click the Manage Privileges link.
Click the link associated with the privilege to administer.
In the Privileges dialog, perform the following tasks:
To change the setting for an application role, individual user, or Catalog group that is listed in the dialog, select either Granted or Denied in the Permission column.
To add application roles, individual users, or Catalog groups for the privilege, click the Add Users/Roles button and complete the Add Application Roles, Catalog Groups, and Users dialog.
Click OK.
Click Back.
Table C-1 lists the privileges that you can manage, along with the application role that is granted access to that privilege by default.
These privileges apply to the Oracle Business Intelligence infrastructure. If your organization uses prebuilt applications, then some privileges might be pre configured. For more information, see the documentation for the application.
Table C-1 Privileges and Default Settings for the Oracle Business Intelligence Infrastructure
| Component | Privilege | Description | Default Role Granted |
|---|---|---|---|
|
Access |
Access to Dashboards |
Allows users to view dashboards. |
BIConsumer |
|
Access |
Access to Answers |
Allows users to access the basic features of the Analysis editor. |
BIAuthor |
|
Access |
Access to Delivers |
Allows users to create and edit agents. |
BIAuthor |
|
Access |
Access to Briefing Books |
Allows users to view and download briefing books. |
BIConsumer |
|
Access |
Access to Administration |
Allows users to access the Administration pages in Presentation Services, |
BIAdministrator |
|
Access |
Access to Segments |
Allows users to access segments in Oracle's Siebel Marketing. |
BIConsumer |
|
Access |
Access to Segment Trees |
Allows users to access segment trees in Oracle's Siebel Marketing. |
BIAuthor |
|
Access |
Access to List Formats |
Allows users to access list formats in Oracle's Siebel Marketing. |
BIAuthor |
|
Access |
Access to Metadata Dictionary |
Allows users to access the metadata dictionary information for subject areas, folders, columns, and levels. For more information, see Section 19.2.1, "Providing Access to Metadata Dictionary Information." |
BIAdministrator |
|
Access |
Access to Oracle BI for Microsoft Office |
See Section C.2.3.3.2, "Access to Oracle BI for Microsoft Office Privilege." |
BIConsumer |
|
Access |
Access to Conditions |
Allows users to create conditions. |
BIAuthor |
|
Access |
Access to KPI Builder |
Allows users to create KPIs. |
BIAuthor |
|
Access |
Access to Scorecard |
Allows users access to Oracle BI Scorecard. |
BIConsumer |
|
Actions |
Create Navigate Actions |
See Section C.2.3.3.1, "Access to Oracle BI Enterprise Edition Actions." |
BIAuthor |
|
Actions |
Create Invoke Actions |
See Section C.2.3.3.1, "Access to Oracle BI Enterprise Edition Actions." |
BIAuthor |
|
Actions |
Save Actions Containing Embedded HTML |
See Section C.2.3.3.1, "Access to Oracle BI Enterprise Edition Actions." |
BIAdministrator |
|
Admin: Catalog |
Change Permissions |
Allows users to modify permissions for catalog objects. |
BIAuthor |
|
Admin: Catalog |
Toggle Maintenance Mode |
Shows the Toggle Maintenance Mode link on the Presentation Services Administration page, which allows users to turn maintenance mode on and off. In maintenance mode, the catalog is read-only; no one can write to it. |
BIAdministrator |
|
Admin: General |
Manage Sessions |
Shows the Manage Sessions link on the Presentation Services Administration page, which displays the Manage Sessions page in which users manage sessions. |
BIAdministrator |
|
Admin: General |
Manage Dashboards |
Allows users to create and edit dashboards, including editing their properties. |
BIAdministrator |
|
Admin: General |
See Session IDs |
Allows users to see session IDs on the Manage Sessions page. |
BIAdministrator |
|
Admin: General |
Issue SQL Directly |
Shows the Issue SQL link on the Presentation Services Administration page, which displays the Issue SQL page in which users enter SQL statements. |
BIAdministrator |
|
Admin: General |
View System Information |
Allows users to view information about the system at the top of the Administration page in Presentation Services. |
BIAdministrator |
|
Admin: General |
Performance Monitor |
Allows users to monitor performance. |
BIAdministrator |
|
Admin: General |
Manage Agent Sessions |
Shows the Manage Agent Sessions link on the Presentation Services Administration page, which displays the Manage Agent Sessions page in which users manage agent sessions. |
BIAdministrator |
|
Admin: General |
Manage Device Types |
Shows the Manage Device Types link on the Presentation Services Administration page, which displays the Manage Device Types page in which users manage device types for agents. |
BIAdministrator |
|
Admin: General |
Manage Map Data |
Shows the Manage Map Data link on the Presentation Services Administration page, which displays the Manage Map Data page in which users edit layers, background maps, and images for map views. |
BIAdministrator |
|
Admin: General |
See Privileged Errors |
Allows users to see privileged error messages. Users can see detailed error messages about database connections or other details when lower level components fail. |
BIAdministrator |
|
Admin: General |
See SQL Issued in Errors |
Allows users to see SQL statements that are returned by the BI Server in error messages. |
BIConsumer |
|
Admin: General |
Manage Marketing Jobs |
Shows the Manage Marketing Jobs link on the Presentation Services Administration page, which displays the Marketing Job Management page in which users manage marketing jobs. |
BIAuthor |
|
Admin: General |
Manage Marketing Defaults |
Shows the Manage Marketing Defaults link on the Presentation Services Administration page, which displays the Manage Marketing Defaults page in which users manage defaults for Oracle's Siebel Marketing application. |
BIAdministrator |
|
Admin: Security |
Manage Catalog Groups |
Shows the Manage Catalog Groups link on the Presentation Services Administration page, which displays the Manage Catalog Groups page in which users edit Catalog groups. |
BIAdministrator |
|
Admin: Security |
Manage Privileges |
Shows the Manage Privileges link on the Presentation Services Administration page, which displays the Manage Privileges page in which users manage the privileges that are described in this table. |
BIAdministrator |
|
Admin: Security |
Set Ownership of Catalog Objects |
Allows users to edit the ownership of objects in the catalog on the Catalog page. |
BIAdministrator |
|
Admin: Security |
User Population - Can List Users |
Allows users to see the list of users for which they can perform tasks such as assigning privileges and permissions. |
BIConsumer, BISystem |
|
Admin: Security |
User Population - Can List Groups |
Allows users to see the list of groups for which they can perform tasks such as assigning privileges and permissions. |
BIConsumer, BISystem |
|
Briefing Book |
Add To or Edit a Briefing Book |
Allows users to see the Add to Briefing Book link on dashboard pages and analyses and the Edit link in briefing books. |
BIAuthor |
|
Briefing Book |
Download Briefing Book |
Allows users to download briefing books. |
BIConsumer |
|
Catalog |
Personal Storage |
Allows users to have write access to their own My Folders folders and can create content there. If users do not have this privilege, then they can receive email alerts but cannot receive dashboard alerts. |
BIConsumer |
|
Catalog |
Reload Metadata |
Allows users to click the Reload Server Metadata link from the Refresh menu in the toolbar of the Subject Areas pane. |
BIAdministrator |
|
Catalog |
See Hidden Items |
Allows users to see hidden items in catalog folders. Users can also select the Show Hidden Items box on the Catalog page. |
BIAuthor |
|
Catalog |
Create Folders |
Allows users to create folders in the catalog. |
BIAuthor |
|
Catalog |
Archive Catalog |
Allows users to archive the folders and objects in the catalog. |
BIAdministrator |
|
Catalog |
Unarchive Catalog |
Allows users to unarchive catalog objects that have been archived previously. |
BIAdministrator |
|
Catalog |
Upload Files |
Allows users to upload files into an existing catalog. |
BIAdministrator |
|
Conditions |
Create Conditions |
Allows users to create or edit named conditions. |
BIAuthor |
|
Dashboards |
Save Customizations |
See Section 19.5, "Controlling Access to Saved Customization Options in Dashboards." |
BIConsumer |
|
Dashboards |
Assign Default Customizations |
See Section 19.5, "Controlling Access to Saved Customization Options in Dashboards." |
BIAuthor |
|
Formatting |
Save SystemWide Column Formats |
Allows users to save systemwide defaults when specifying formats for columns. |
BIAdministrator |
|
My Account |
Access to My Account |
Allows users to access the My Account dialog. |
BIConsumer |
|
My Account |
Change Preferences |
Allows users to access the Preferences tab of the My Account dialog. |
BIConsumer |
|
My Account |
Change Delivery Options |
Allows users to access the Delivery Options tab of the My Account dialog. |
BIConsumer |
|
Answers |
Create Views |
Allows users to create views. |
BIAuthor |
|
Answers |
Create Prompts |
Allows users to create prompts. |
BIAuthor |
|
Answers |
Access Advanced Tab |
Allows users to access the Advanced tab in the Analysis editor. |
BIAuthor |
|
Answers |
Edit Column Formulas |
Allows users to edit column formulas. |
BIAuthor |
|
Answers |
Save Content with HTML Markup |
Allows users to save objects such as views and actions that contain HTML code. |
BIAdministrator |
|
Answers |
Enter XML and Logical SQL |
Allows users to use the Advanced SQL tab. |
BIAuthor |
|
Answers |
Edit Direct Database Analysis |
Allows users to create and edit requests that are sent directly to the back-end data source. |
BIAdministrator |
|
Answers |
Create Analysis from Simple SQL |
Allows users to select the Create Analysis from Simple SQL option in the Select Subject Area list. |
BIAdministrator |
|
Answers |
Create Advanced Filters and Set Operations |
Allows users to click the Combine results based on union, intersection, and difference operations button from the Criteria tab in the Analysis editor. |
BIAuthor |
|
Answers |
Save Filters |
Allows users to save filters |
BIAuthor |
|
Answers |
Execute Direct Database Analysis |
Allows users to issue requests directly to the back-end data source. |
BIAdministrator |
|
Delivers |
Create Agents |
Allows users to create agents. |
BIAuthor |
|
Delivers |
Publish Agents for Subscription |
Allows users to publish agents for subscription. |
BIAuthor |
|
Delivers |
Deliver Agents to Specific or Dynamically Determined Users |
Allows users to deliver agents to other users. |
BIAdministrator |
|
Delivers |
Chain Agents |
Allows users to chain agents. |
BIAuthor |
|
Delivers |
Modify Current Subscriptions for Agents |
Allows users to modify the current subscriptions for agents, including unsubscribing users. |
BIAdministrator |
|
Proxy |
Act As Proxy |
Allows users to act as proxy users for other users, as described in Section C.5, "Enabling Users to Act for Others." |
Denied: BIConsumer |
|
RSS Feeds |
Access to RSS Feeds |
Allows users to subscribe to and receive RSS feeds with alerts and contents of folders. If Presentation Services uses the HTTPS protocol, then the RSS Reader that you use must also support the HTTPS protocol. |
BIAuthor |
|
Scorecard |
Create/Edit Scorecards |
Allows users to create and edit scorecards. |
BIAuthor |
|
Scorecard |
View Scorecards |
Allows users to view scorecards. |
BIConsumer |
|
Scorecard |
Create/Edit Objectives |
Allows users to create and edit objectives. |
BIAuthor |
|
Scorecard |
Create/Edit Initiatives |
Allows users to create and edit initiatives. |
BIAuthor |
|
Scorecard |
Create Views |
Allows users to create and edit scorecard views, such as strategy trees. |
BIAuthor |
|
Scorecard |
Create/Edit Causes and Effects Linkages |
Allows users to create and edit cause and effect relationships. |
BIAuthor |
|
Scorecard |
Create/Edit Perspectives |
Allows users to create and edit perspectives. |
BIAdministrator |
|
Scorecard |
Add Annotations |
Allows users to add comments to KPIs and scorecard components. |
BIConsumer |
|
Scorecard |
Override Status |
Allows users to override statuses of KPIs and scorecard components. |
BIConsumer |
|
Scorecard |
Create/Edit KPIs |
Allows users to create and edit KPIs. |
BIAuthor |
|
Scorecard |
Add Scorecard Views to Dashboards |
Allows users to add scorecard views (such as strategy trees) to dashboards. |
BIConsumer |
|
List Formats |
Create List Formats |
Allows users to create list formats in Oracle's Siebel Marketing. |
BIAuthor |
|
List Formats |
Create Headers and Footers |
Allows users to create headers and footers for list formats in Oracle's Siebel Marketing. |
BIAuthor |
|
List Formats |
Access Options Tab |
Allows users to access the Options tab for list formats in Oracle's Siebel Marketing. |
BIAuthor |
|
List Formats |
Add/Remove List Format Columns |
Allows users to add and remove columns for list formats in Oracle's Siebel Marketing. |
BIAdministrator |
|
Segmentation |
Create Segments |
Allows users to create segments in Oracle's Siebel Marketing. |
BIAuthor |
|
Segmentation |
Create Segment Trees |
Allows users to create segment trees in Oracle's Siebel Marketing. |
BIAuthor |
|
Segmentation |
Create/Purge Saved Result Sets |
Allows users to create and purge saved result sets in Oracle's Siebel Marketing. |
BIAdministrator |
|
Segmentation |
Access Segment Advanced Options Tab |
Allows users to access the Segment Advanced Options tab in Oracle's Siebel Marketing. |
BIAdministrator |
|
Segmentation |
Access Segment Tree Advanced Options Tab |
Allows users to access the Segment Tree Advanced Options tab in Oracle's Siebel Marketing. |
BIAdministrator |
|
Segmentation |
Change Target Levels within Segment Designer |
Allows users to change target levels within the Segment Designer in Oracle's Siebel Marketing. |
BIAdministrator |
|
SOAP |
Access SOAP |
Allows users to access various web services. |
BIConsumer, BISystem |
|
SOAP |
Impersonate as System User |
Allows users to impersonate a system user using a web service. |
BISystem |
|
SOAP |
Access MetadataService Service |
Allows users to access the MetadataService web service. |
BIConsumer, BISystem |
|
SOAP |
Access AnalysisExportViewsService Service |
Allows users to access the ReportingEditingService web service. |
BIConsumer |
|
SOAP |
Access ReportingEditingService Service |
Allows users to access the ReportingEditingService web service. |
BIConsumer, BISystem |
|
SOAP |
Access ConditionEvaluationService Service |
Allows users to access the ConditionEvaluationService web service. |
BIConsumer, BISystem |
|
SOAP |
Access ReplicationService Service |
Allows users to access the ReplicationService web service to replicate the Oracle BI Presentation Catalog. |
BISystem |
|
SOAP |
Access CatalogIndexingService Service |
Allows users to access the CatalogIndexingService web service to index the Oracle BI Presentation Catalog for use with full-text search. |
BISystem |
|
SOAP |
Access DashboardService Service |
Allows users to access the DashboardService web service. |
BIConsumer, BISystem |
|
SOAP |
Access SecurityService Service |
Allows users to access the SecurityService web service. |
BIConsumer, BISystem |
|
SOAP |
Access ScorecardMetadataService Service |
Allows users to access the ScorecardMetadataService web service. |
BIConsumer, BISystem |
|
SOAP |
Access ScorecardAssessmentService Service |
Allows users to access the ScorecardAssessmentService web service. |
BIConsumer, BISystem |
|
SOAP |
Access HtmlViewService Service |
Allows users to access the HtmlViewServiceService web service. |
BIConsumer, BISystem |
|
SOAP |
Access CatalogService Service |
Allows users to access the CatalogService web service. |
BIConsumer, BISystem |
|
SOAP |
Access IBotService Service |
Allows users to access the IBotService web service. |
BIConsumer, BISystem |
|
SOAP |
Access XmlGenerationService Service |
Allows users to access the XmlGenerationService web service. |
BIConsumer, BISystem |
|
SOAP |
Access JobManagementService Service |
Allows users to access the JobManagementService web service. |
BIConsumer, BISystem |
|
SOAP |
Access KPIAssessmentService Service |
Allows users to access the JKPIAssessmentService web service. |
BIConsumer, BISystem |
|
Subject Area (by its name) |
Access within Oracle BI Answers |
Allows users to access the specified subject area within the Answers editor. |
BIAuthor |
|
View Analyzer |
Add/Edit AnalyzerView |
Allows users to access the Analyzer view. |
BIAdministrator |
|
View Column Selector |
Add/Edit Column SelectorView |
Allows users to create and edit column selector views. |
BIAuthor |
|
View Compound |
Add/Edit CompoundView |
Allows users to create and edit compound layouts. |
BIAuthor |
|
View Graph |
Add/Edit GraphView |
Allows users to create and edit graph views. |
BIAdministrator |
|
View Funnel |
Add/Edit FunnelView |
Allows users to create and edit funnel graph views. |
BIAuthor |
|
View Gauge |
Add/Edit GaugeView |
Allows users to create and edit gauge views. |
BIAuthor |
|
View Filters |
Add/Edit FiltersView |
Allows users to create and edit filters. |
BIAuthor |
|
View Dashboard Prompt |
Add/Edit Dashboard PromptView |
Allows users to create and edit dashboard prompts. |
BIAuthor |
|
View Static Text |
Add/Edit Static TextView |
Allows users to create and edit static text views. |
BIAuthor |
|
View Legend |
Add/Edit Legend View |
Allows users to create and edit legend views. |
BIAuthor |
|
View Map |
Add/Edit MapView |
Allows users to create and edit map views. |
BIAuthor |
|
View Narrative |
Add/Edit NarrativeView |
Allows users to create and edit narrative views. |
BIAuthor |
|
View Nested Request |
Add/Edit Nested RequestView |
Allows users to create and edit nested analyses. |
BIAuthor |
|
View No Results |
Add/Edit No ResultsView |
Allows users to create and edit no result views. |
BIAuthor |
|
View Pivot Table |
Add/Edit Pivot TableView |
Allows users to create and edit pivot table views. |
BIAuthor |
|
View Report Prompt |
Add/Edit Report PromptView |
Allows users to create and edit prompts. |
BIAuthor |
|
View Create Segment |
Add/Edit Create SegmentView |
Allows users to create and edit segment views. |
BIAuthor |
|
View Logical SQL |
Add/Edit Logical SQLView |
Allows users to create and edit logical SQL views. |
BIAuthor |
|
View Table |
Add/Edit TableView |
Allows users to create and edit table views. |
BIAuthor |
|
View Create Target List |
Add/Edit Create Target ListView |
Allows users to create and edit target list views. |
BIAuthor |
|
View Ticker |
Add/Edit TickerView |
Allows users to create and edit ticker views. |
BIAuthor |
|
View Title |
Add/Edit TitleView |
Allows users to create and edit title views. |
BIAuthor |
|
View View Selector |
Add/Edit View SelectorView |
Allows users to create and edit view selector views. |
BIAuthor |
|
Write Back |
Write Back to Database |
Grants the right to write data into the data source. |
Denied: BIConsumer |
|
Write Back |
Manage Write Back |
Grants the right to manage write back requests. |
BIAdministrator |
You must set the Action privileges, which determine whether the Actions functionality is available to users and specify which user types can create Actions. The following list describes these privileges:
Create Navigate Actions — Determines which users can create a Navigate action type. The sessions of users who are denied this privilege do not contain any of the user interface components that allow them to create Navigate Actions. For example, if a user is denied this privilege and chooses to create an action from the Oracle BI Enterprise Edition global header, the dialog where the user selects an action type does not include the Navigate Actions options (Go to BI Content, Go to a Web Page, and so on). However, users who are denied this privilege can add saved actions to analyses and dashboards. And, users who are denied this privilege can execute an action from an analysis or dashboard that contains an action.
Create Invoke Actions — Determines which users can create an Invoke action type. The sessions of user who are denied this privilege do not contain any of the user interface components that allow them to create Invoke Actions. For example, if a user is denied this privilege and chooses to access the agent editor's Actions tab and clicks the Add New Action button, the dialog where the user selects the action type does not include the Invoke Actions options (Invoke a Web Service, Invoke an HTTP Request, and so on). However, users who are denied this privilege can add saved actions to analyses and dashboards. And, users who are denied this privilege can execute an action from an analysis or dashboard that contains an action.
Save Actions Containing Embedded HTML — Determines which users can embed HTML code in the customization of web service action results. Use care in assigning this privilege, because it poses a security risk to allow users to run HTML code.
The Access to Oracle BI for Microsoft Office privilege shows the following options for the Download BI Desktop Tools link in the Get Started area of the Oracle BI EE Home page:
Oracle BI for MS Office: Downloads the installation file for the Oracle BI Add-in for Microsoft Office.
Smart View: Downloads the installation file for Oracle Hyperion Smart View.
The Access to Oracle BI for Microsoft Office privilege does not affect the display of the Copy link for analyses. The link is always available there.
The location of the installation file to download for the Oracle BI Add-in for Microsoft Office is specified by default in the BIforOfficeURL element in the instanceconfig.xml file. For more information on using the Oracle BI Add-in for Microsoft Office and the Copy option, see Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Using the Session Management page in Presentation Services Administration, you can view information about active users and running analyses, cancel requests, and clear the cache.
To manage sessions in Presentation Services:
From the Home page in Presentation Services, select Administration.
Click the Manage Sessions link.
The Session Management screen is displayed with the following tables:
The Sessions table, which gives information about sessions that have been created for users who have logged in:
The Cursor Cache table, which shows the status of analyses:
To cancel all running requests:
Click Cancel Running Requests.
Click Finished.
To cancel one running analysis:
In the Cursor Cache table, identify the analysis and click the Cancel link in the Action column.
The user receives a message indicating that the analysis was canceled by an administrator.
In the Cursor Cache table, identify the analysis and click Close All Cursors.
Click Finished.
To clear the cache entry associated with an analysis:
In the Cursor Cache table, identify the analysis and click the Close link in the Action column.
To view the query file for information about an analysis:
In the Cursor Cache table, identify the analysis and click the View Log link.
|
Note: Query logging must be turned on for data to be saved in this log file. |
Permissions and privileges can be assigned to users directly or through membership in application roles or Catalog groups. From another perspective, permissions and privileges can be assigned explicitly or effectively. Effective permissions and privileges are assigned indirectly through inheritance from application roles or Catalog groups, which is the recommended approach for assignments.
This section contains the following topics:
Section C.3.1, "Rules for Inheritance for Permissions and Privileges"
Section C.3.2, "Example of Inherited Privileges for Application Roles"
Section C.3.3, "Example of Inherited Privileges for Catalog Groups"
The following list describes the rules of inheritance for permissions and privileges:
Any permissions or privileges granted explicitly to a user override any permissions or privileges inherited from the application roles or Catalog groups to which the user belongs.
If a user belongs to two application roles or Catalog groups and both are granted permissions, then the least restrictive permissions are given to the user.
For example, if one application role allows Open access and another allows Modify access, then the least restrictive access would be granted; in this example, Open access.
|
Note: The exception to this is if one of the two application roles or Catalog groups is explicitly denied the permissions, in which case the user is denied. |
If a user belongs to Application Role X, and Application Role X is a member of Application Role Y, then any permissions assigned to Application Role X override any permissions assigned to Application Role Y. The same holds true if X and Y are Catalog groups.
For example, if Marketing has Open permissions, Marketing Administrators, which is a member of Marketing, can have Full Control permission.
If a Catalog group is specified along with an application role in the Permissions dialog in Presentation Services, then the Catalog group takes precedence.
For example, suppose that for a certain object, the BIAdministrator role has Read-Only permission and the Admin Catalog Group has Full Control permission. If a user signs in who is a member of both the BIAdministrator role and the Admin Catalog Group, then he is granted full access to the object.
Explicitly denying access takes precedence over any other permissions or privileges.
Figure C-1 shows an example of how privileges are inherited through application roles. At the top of the diagram is a rectangle labeled User1, which specifies that User1 is a member of Role1 and Role2. Attached beneath the User1 rectangle are two more rectangles — one on the left that represents Role1 and one on the right that represents Role2.
The Role1 rectangle specifies that Role1 has no access to DashboardA and is a member of Role3 and Role4.
The Role2 rectangle specifies that Role2 has Open access to DashboardD, is a member of Role5, and has no access to DashboardE.
Attached beneath the Role1 rectangle are two more rectangles — one on the left that represents Role3 and one on the right that represents Role4:
The Role3 rectangle specifies that Role3 has Open access to DashboardB.
The Role4 rectangle specifies that Role4 has Full Access to DashboardC and Open access to DashboardA.
And finally, attached beneath the Role2 rectangle is a rectangle that represents Role5. The Role5 rectangle specifies that Role5 has Modify access to Dashboard D and Open access to DashboardE.
Figure C-1 Example of Inheritance of Permissions Using Roles
In this example:
User1 is a direct member of Role1 and Role2, and is an indirect member of Role3, Role4, and Role5.
The permissions and privileges from Role1 are no access to DashboardA, Open access to DashboardB, and Full Control for DashboardC.
If one application role is a member of a second application role, then any permissions assigned to the first application role override any permissions assigned to the first role. Therefore, the inherited permissions and privileges from Role2 include Modify access to DashboardD from Role5.
Specifically denying access always takes precedence over any other settings. Therefore, Role1's denial of access to DashboardA overrides Role4's Open access. The result is that Role1 has no access to DashboardA. Likewise, Role5 has no access to DashboardE, because access to that dashboard is explicitly denied for Role2.
The total permissions and privileges granted to User1 are as follows:
No access to DashboardA and DashboardE, because access is specifically denied.
Open access to DashboardB.
Full Control for DashboardC.
Modify access to DashboardD.
Any permissions or privileges granted explicitly to a Catalog group take precedence over permissions or privileges granted to an application role. For example, suppose that have an application role called Marketing_US that has Full Access to the Marketing Dashboard. You want to restrict a small set of the users in the Marketing_US role to not have access to that dashboard. To do so, you create a Catalog group called Marketing_SanJose and add the appropriate users as members of that group. You then deny the Marketing_SanJose Catalog group access to the Marketing Dashboard. Even though those users belong to the Marketing_US role, they are denied access to the Marketing Dashboard.
This section contains the following topics on providing shared dashboards for users:
The Oracle BI Presentation Catalog has two main folders:
My Folders — Contains the personal storage for individual users. Includes a Subject Area Contents folder where you save objects such as calculated items and groups.
Shared Folders — Contains objects and folders that are shared across users. Dashboards that are shared across users are saved in a Dashboards subfolder under a common subfolder under the /Shared Folders folder
|
Note: If a user is given permission to an analysis in the Oracle BI Presentation Catalog that references a subject area to which the user does not have permission, then the Oracle BI Server still prevents the user from executing the analysis. |
After setting up the Oracle BI Presentation Catalog structure and setting permissions, you can create shared dashboards and content for use by others.
One advantage to creating shared dashboards is that pages that you create in the shared dashboard are available for reuse. Users can create their own dashboards using the pages from your shared dashboards and any new pages that they create. You can add pages and content as described in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
If you plan to allow multiple users to modify a shared default dashboard, then consider putting these users into an application role. For example, suppose that you create an application role called Sales and create a default dashboard called SalesHome. Of the 40 users that have been assigned the Sales application role, suppose that there are three who must have the ability to create and modify content for the SalesHome dashboard. Create a SalesAdmin application role, with the same permissions as the primary Sales application role. Add the three users who are allowed to make changes to the SalesHome dashboard and content to this new SalesAdmin application role, and give this role the appropriate permissions in the Oracle BI Presentation Catalog. This allows those three users to create and modify content for the SalesHome dashboard. If a user no longer requires the ability to modify dashboard content, then you can change the user's role assignment to Sales. If an existing Sales role user must have the ability to create dashboard content, then the user's role assignment can be changed to SalesAdmin.
For more information about creating shared dashboards, see Section 19.1, "Managing Dashboards."
Before releasing dashboards and content to the user community, perform some tests.
To test the dashboard:
Verify that users with appropriate permissions can correctly access it and view the intended content.
Verify that users without appropriate permissions cannot access the dashboard.
Verify that styles and skins are displayed as expected, and that other visual elements are as expected.
Correct any problems you find and test again, repeating this process until you are satisfied with the results.
After testing is complete, notify the user community that the dashboard is available, ensuring that you provide the relevant network address.
This section contains the following topics on enabling users to act for others:
You can enable one user to act for another user in Oracle BI Presentation Services. When a user (called the proxy user) acts as another (called the target user), the proxy user can access the objects in the catalog for which the target user has permission.
Enabling a user to act for another is useful, for example, when a manager wants to delegate some of his work to one of his direct reports or when IT support staff wants to troubleshoot problems with another user's objects.
See Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition for information on how users enable others to act for them.
When you enable a user to be a proxy user, you also assign an authority level (called the proxy level). The proxy level determines the privileges and permissions granted to the proxy user when accessing the catalog objects of the target user. The following list describes the proxy levels:
Restricted — Permissions are read-only to the objects to which the target user has access. Privileges are determined by the proxy user's account (not the target user's account).
For example, suppose a proxy user has not been assigned the Access to Answers privilege, and the target user has. When the proxy user is acting as the target user, the target user cannot access Answers.
Full — Permissions and privileges are inherited from the target user's account.
For example, suppose a proxy user has not been assigned the Access to Answers privilege, and the target user has. When the proxy user is acting as the target user, the target user can access Answers.
When you have enabled a user to act as a proxy user, that user can display the Act As option in the global header of Presentation Services to select the target user to act as, provided the Act As Proxy privilege has been set.
|
Tip: Before a proxy user can act as a target user, the target user must have signed into Presentation Services at least once and accessed a dashboard. |
To enable users to act for others, perform the following tasks:
Section C.5.3.1, "Defining the Association Between Proxy Users and Target Users"
Section C.5.3.2, "Creating Session Variables for Proxy Functionality"
Section C.5.3.3, "Modifying the Configuration File Settings for Proxy Functionality"
Section C.5.3.4, "Creating a Custom Message Template for Proxy Functionality"
You define the association between proxy users and target users in the database by identifying, for each proxy user/target user association, the following:
ID of the proxy user
ID of the target user
Proxy level (either full or restricted)
For example, you might create a table called Proxies in the database that looks like this:
| proxyId | targetId | proxyLevel |
|---|---|---|
| Ronald | Eduardo | full |
| Timothy | Tracy | restricted |
| Pavel | Natalie | full |
| William | Sonal | restricted |
| Maria | Imran | restricted |
After you define the association between proxy users and target users, you must import the schema to the physical layer of the Oracle BI Server. For information on importing a schema, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
To authenticate proxy users, you must create the following two session variables along with their associated initialization blocks. For both variables, you must modify the sample SQL statement according to the schema of the database.
PROXY — Use this variable to store the name of the proxy user.
Use the initialization block named ProxyBlock and include code such as the following:
select targetIdfrom Proxieswhere 'VALUEOF(NQ_SESSION.RUNAS)'=targetId and ':USER'=proxyId
PROXYLEVEL — Use this optional variable to store the proxy level, either Restricted or Full. If you do not create the PROXYLEVEL variable, then the Restricted level is assumed.
Use the initialization block named ProxyLevel and include code such as the following:
select proxyLevelfrom Proxieswhere 'VALUEOF(NQ_SESSION.RUNAS)'=targetId and ':USER'=proxyId
For more information on creating session variables, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
Use various elements in the instanceconfig.xml file to configure the proxy functionality.
Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, "Using a Text Editor to Update Oracle Business Intelligence Configuration Settings".
To manually configure for proxy functionality:
Open the instanceconfig.xml file for editing, as described in Section 3.6, "Where are Configuration Files Located?"
Locate the section in which you must add the elements that are described in the following list:
LogonParam: Serves as the parent element for the TemplateMessageName and MaxValues elements.
TemplateMessageName: Specifies the name of the custom message template in the Custom Messages folder that contains the SQL statement to perform tasks related to displaying proxy and target users. The default name is LogonParamSQLTemplate.
The name that you specify in the TemplateMessageName element must match the name that you specify in the WebMessage element in the custom message file. For more information, see Section C.5.3.4, "Creating a Custom Message Template for Proxy Functionality."
MaxValues: Specifies the maximum number of target users to be listed in the User box in the Act As dialog box. If the number of target users for a proxy user exceeds this value, then an edit box, where the proxy user can type the ID of a target user, is shown rather than a list of target users. The default is 200.
Include the elements and their ancestor elements as appropriate, as shown in the following example:
<LogonParam><TemplateMessageName>LogonParamSQLTemplate</TemplateMessageName><MaxValues>100</MaxValues></LogonParam>
Save your changes and close the file.
Restart Oracle Business Intelligence.
You must create a custom message template for the proxy functionality that contains the SQL statement to perform the following tasks:
Obtain the list of target users that a proxy user can act as. This list is displayed in the User box in the Act As dialog box.
Verify whether the proxy user can act as the target user.
Obtain the list of proxy users that can act as the target user. This list is displayed on the target user's My Account screen.
In the custom message template, you place the SQL statement to retrieve this information in the following XML elements:
| Element | Description |
|---|---|
| getValues | Specifies the SQL statement to return the list of target users and corresponding proxy levels.
The SQL statement must return either one or two columns, where the:
|
| verifyValue | Specifies the SQL statement to verify if the current user can act as the specified target user.
The SQL statement must return at least one row if the target user is valid or an empty table if the target user is invalid. |
| getDelegateUsers | Specifies the SQL statement to obtain the list of proxy users that can act as the current user and their corresponding proxy levels.
The SQL statement must return either one or two columns, where the:
|
For information on the directory for storing custom message templates, see Section 22.5.3, "Customizing XML Messages." You can create the custom message template in one of the following files:
The original custom message file in the directory
A separate XML file in the directory
To create the custom message template:
To create the custom message template in the original custom message file:
Make a backup of the original custom message file in a separate directory.
Make a development copy in a different directory and open it in a text or XML editor.
To create the custom message template in a separate XML file, create and open the file in the ORACLE_INSTANCE\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obipsn\msgdb\l_xx\customMessages directory.
Start the custom message template by adding the WebMessage element's begin and end tags. For example:
<WebMessage name="LogonParamSQLTemplate"> </WebMessage>
|
Note: The name that you specify in the WebMessage element must match the name that you specify in the TemplateMessageName element in the instanceconfig.xml file. For information, see Section C.5.3.3, "Modifying the Configuration File Settings for Proxy Functionality." |
After the </WebMessage> tag:
Add the <XML> and </XML> tags
Between the <XML> and </XML> tags, add the <logonParam name="RUNAS"> and </logonParam> tags.
Between the <logonParam name="RUNAS"> and </logonParam> tags, add each of the following tags along with its corresponding SQL statements:
<getValues> and </getValues>
<verifyValue> and </verifyValue>
<getDelegateUsers> and </getDelegateUsers>
The following entry is an example:
<XML><logonParam name="RUNAS"><getValues>select targetIdfrom Proxieswhere proxyId='@{USERID}'</getValues><verifyValue>select targetIdfrom Proxieswhere proxyId ='@{USERID}'and targetId='@{VALUE}'</verifyValue><getDelegateUsers>select proxyId, proxyLevelfrom Proxieswhere targetId ='@{USERID}'</getDelegateUsers></logonParam></XML>
(Note that you must modify the example SQL statement according to the schema of the database.)
If you created the custom message template in the development copy of the original file, then replace the original file in the customMessages directory with the newly edited file.
Test the new file.
(Optional) If you created the custom message template in the development copy of the original file, then delete the backup and development copies.
Load the custom message template by either restarting the server or by clicking the Reload Files and Metadata link on the Presentation Services Administration screen. For information on the Administration page, see Section C.2.1, "Understanding the Administration Pages."
For each user whom you want to enable as a proxy user or for each application role or Catalog group whose members you want to enable as proxy users, you must grant the Act As Proxy privilege. For information on how to assign privileges, see Section C.2.3.2, "Setting Privileges in Oracle BI Presentation Services Administration."
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|