Skip Headers

Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher (Oracle Fusion Applications Edition)
Release 11g (11.1.1)
Part Number E20837-01
Go to Table of Contents
Go to previous page
Go to next page
View PDF

Other Security Topics

This chapter covers the following topics:

Enabling a Local Superuser

BI Publisher allows you to define an administration Superuser. Using the Superuser credentials you can directly access the BI Publisher administrative functions without logging in through the defined security model.

Set up this Superuser to ensure access to all administrative functions in case of failures with the configured security model. It is highly recommended that you set up a Superuser.

  1. Click Administration.

  2. Under Security Center click Security Configuration.

  3. Under Local Superuser, select the box and enter the credentials for the Superuser.

    the picture is described in the document text

  4. Restart the BI Publisher application.

Enabling a Guest User

BI Publisher allows you configure public access to specific reports by defining a "Guest" folder. Any user can access the reports in this folder without entering credentials. Note that Guest access is not supported if you are using a shared catalog with Oracle Business Intelligence Enterprise Edition.

Important: Guest access is not supported with Single Sign-On.

Note that all objects required to view a report must be present in the Guest folder because the Guest folder is the only folder the guest user will have any access rights to. Therefore the report and the data model must be present in the Guest folder as well as Sub Templates and Style Templates, if applicable. The guest user will have read access only.

The Guest user must also be granted access to the report data source.

To enable guest access:

  1. Under Shared Folders, create the folder to which you want to grant public access.

  2. Click Administration.

  3. Under Security Center select Security Configuration.

  4. Under Guest Access, select Allow Guest Access.

  5. Enter the name of the folder that you created for public access.

    the picture is described in the document text

  6. Restart the BI Publisher application.

  7. Add the objects to the Guest folder that you want the guest users to access: folders, reports, data models, Sub Templates and Style Templates.

    Note: The report must reference the data model that is stored in the guest folder. Therefore, if you copy a report with its data model from another location, ensure to open the report and reselect the data model so that the report references the data model inside the guest folder.

    Similarly, any references to Sub Templates or Style Templates must also be updated.

  8. Grant access to the data sources used by data models in your Guest folder. See Setting Up Data Sources for information on granting Guest access to a data source.

Users who access BI Publisher will see the Guest button on the log on page. Users can select this button and view the reports in your chosen guest folder without presenting credentials.

Configuring BI Publisher for Secure Socket Layer (SSL) Communication

If BI Publisher is communicating with other applications over SSL you may need to perform additional configuration to ensure operability.

Important: It is strongly recommended that you enable Secure Socket Layer (HTTPS) on the middle tier hosting the Web services because the trusted username/password that is passed can be intercepted. This also pertains to Web services that are used for communication between BI Publisher and Oracle BI Presentation Services.

Pointing BI Publisher to the System-Wide Keystore

By default, BI Publisher uses the Java keystore: {java.home}/lib/security/cacerts

If you are using a different location as your keystore, set the JAVA_OPTS environment variable for your Web server to tell the BI Publisher server where to find the keystore, as follows:

set<keystore file>

Importing Certificates for Web Services Protected by SSL

If you make calls to Web services that are protected via Secure Sockets Layer (SSL) you must export the certificate from the Web server hosting the Web service and import it into the Java keystore on the machine running BI Publisher.

  1. Navigate to the HTTPS site where the WSDL resides.

  2. Download the certificate following the prompts (the prompts you see will vary depending on the browser you are using).

  3. Install the Certificate into your keystore using the Java keytool, as follows:

     keytool -import -file <certfile> -alias <certalias> -keystore <keystore file>
  4. Restart the application server.

These steps should not be required if the server certificate is linked to some certificate authority (such as Verisign). But if the Web service server is using a self-generated certificate (for example, in a testing environment), then these steps will be required.

Configuring the Delivery Manager

If you wish to use the default certificates built-in with BI Publisher, no further configuration is required. SSL will work with the default certificate if the server uses the certificate signed by a trusted certificate authority such as Verisign.

If the user uses the SSL with a self-signed certificate, the certificate information must be entered in the Delivery Configuration page. A self-signed certificate means the certificate is signed by a non-trusted certificate authority (usually the user).

Configuring Proxy Settings

To use external Web Services or HTTP data sources when your BI Publisher server is set up behind a firewall or requires a proxy to access the internet, you must configure Oracle WebLogic Server to be aware of the proxy.

Add the following to

-Dhttp.proxyPort=80 ${EXTRA_JAVA_PROPERTIES}"


is the proxy host.

Note that for communication between BI Publisher and the other components of Oracle BI Enterprise Edition, you must also set the http.nonProxyHosts JVM parameter. This property indicates the hosts that BI Publisher will connect to directly and not through the proxy server. Specify the list of hosts, each separated by a |, and in addition a wildcard character (*) can be used for matching. For example: