Click Customize at the bottom of the Develop tab for the report. Connecting to Oracle Portal

Deploying Reports in Oracle Portal 16-27

16.5.1 Resolving Reports-Portal Integration Error When Attempting Create Resource

In Oracle Portal, when configuring Oracle Reports Security settings for Reports Definition File Access, you may encounter an error when editing a report definition file, when you click Run or Run as Portlet. 500 Internal Server Error Unexpected Error. Please contact Administrator This error occurs when all of the following conditions are true: ■ Running in an Interop deployment which allows for a mixed 9.0.29.0.4 environment, with 9.0.4 MT mid-tier, 9.0.4 IM Identity Management, and 9.0.2 MR metadata repository configured to run together. ■ Running Oracle Reports within Oracle Portal, using the SSOCONN parameter. ■ The connection resource specified in the SSOCONN parameter has not been created in the Oracle Internet Directory server. To implement the workaround, perform the following steps:

1. In the 9.0.4 IM ORACLE_HOME, open the following file in a text editor:

ORACLE_HOMEApacheApacheconfmod_osso.conf 2. Add the following flag: OssoRedirectByForm on For example: IfModule mod_osso.c OssoIpCheck off OssoIdleTimeout off OssoConfigFile private1iasinstinstall_set1904infraApacheApacheconfossoosso.conf OssoRedirectByForm on IfModule 16-28 Publishing Reports to the Web with Oracle Reports Services 17 Configuring and Administering OracleAS Single Sign-On 17-1 17 Configuring and Administering OracleAS Single Sign-On Oracle Application Server Single Sign-On OracleAS Single Sign-On enables you to establish a unique identity for each user, and tie that identity to the resources and data sources unique to that user. For example, a user might log in to an environment such as Oracle Portal, which enables them to access certain reports and printers for which they have the necessary privileges. When they choose to run a report from this environment, they can access the necessary data sources for the report because their data source credentials are stored with the single user identity used to login to Oracle Portal. Thus, logging in once provides them access to all of the resources and data sources they require to run their reports. Because Oracle Reports Services provides a flexible approach to security, you can implement many variations of this configuration. For example, you might choose not to store data source credentials with the single user identity. Or you might prefer to use direct URLs for launching reports rather than a platform like Oracle Portal. If your reports are public and do not require any security, then you might choose to turn off report security altogether. This chapter describes how you can implement and administer various configurations of OracleAS Single Sign-On with Oracle Reports Services. ■ Prerequisites ■ Configuring Out-of-the-Box OracleAS Single Sign-On ■ Administering OracleAS Single Sign-On ■ Choosing the Connecting Entity for Oracle Internet Directory ■ Changing the Reports Servlet Port to Be Protected by Single Sign-On ■ Oracle Forms Services Security Considerations

17.1 Prerequisites

OracleAS Single Sign-On can be implemented only in a secure server environment. This means that you must have a security policy in place in your Reports Server configuration file before you can consider implementing OracleAS Single Sign-On with Oracle Reports Services. For more information, refer to Chapter 15, Securing Oracle Reports Services . With OracleAS Single Sign-On, your administrator establishes a user identity for each user. The administrator does this in Oracle Internet Directory, through its user interface, the Oracle Delegated Administration Services. You can access Oracle