Under Configure Resource Type Information, click Create and you should see a

Configuring and Administering OracleAS Single Sign-On 17-15 Example Entry in the LDIF file: dn: cn=Virtual Application Group, orclApplicationCommonName=reportsApp_Group.us.oracle.com_C7543D42A9E26726E0340 80020A46EE2, cn=Reports, cn=Products, cn=OracleContext changetype: modify add: uniquemember uniquemember: orclApplicationCommonName=reportsApp_serv1.us.oracle.com_A8654E53B0F37837F1451 91131B57FF3, cn=Reports, cn=Products, cn=OracleContext Corresponding ldapmodify command on the command line: ldapmodify -D cn=orcladmin -w welcome1 -h reportsApp_Group.us.oracle.com -p 389 -f mergeentity.ldif

17.5 Changing the Reports Servlet Port to Be Protected by Single Sign-On

After you install Oracle Reports 11g Release 1 11.1.1, the following ports are registered, by default: ■ If WebCache is installed, the WebCache port is registered. ■ If only Oracle HTTP Server no webcache is installed, the Oracle HTTP Server port is registered. To change the Reports Servlet port that must be protected by Single Sign-On: 1. Navigate to the OracleAS Single Sign-On Partner Application Administration page: http:oidhost:oidportplsorasso

2. In the Oracle Single Sign-On Server Administration home page, click Single

Sign-On Server Administration . The Single Sign-On Server Administration page is displayed.

3. Click Administer Partner Applications. The Administer Partner Applications

home page is displayed.

4. Select the host and port related to Reports Servlet, and click Edit. The Partner

Application Login page is displayed.

5. Enter new parameters in Name, Home URL, Success URL, Logout URL fields.

6. Click Apply.

17.6 Oracle Forms Services Security Considerations

The default configuration for Oracle Fusion Middleware Forms Services does not run in OracleAS Single Sign-On SSO mode. The default configuration for Oracle Reports Services does run in SSO mode. Oracle Forms Services applications calling integrated Oracle Reports Services using the RUN_REPORT_OBJECT built-in procedure will not experience any problems when Oracle Forms Services is running in non-SSO mode and Oracle Reports Services is Note: If you are using an SSL port, specify HTTPS instead of HTTP. For more information, see Section 8.14, Enabling HTTPS for Oracle Reports . 17-16 Publishing Reports to the Web with Oracle Reports Services running in Single Sign-On mode as long as the Reports Server and the requested report are not registered in Oracle Portal. Other Requirements: ■ The property Reports Server must be set explicitly for all report objects in the Oracle Forms Services module. ■ If a Reports Server other than the default is being used, that server must be started using Oracle Enterprise Manager. ■ The system variable REPORTS_PATH must be modified in the file ORACLE_ INSTANCEconfigreportsbinreports.sh to reference the path of the reports to be run. ■ The first time Reports Server is started, it creates a configuration file called rwserver.conf located in the ORACLE_ INSTANCE\config\ReportsServerComponent\server_name directory. ■ The default status of Reports Server is secure. To change the Reports Server status to non-secure, modify ORACLE_ INSTANCE\config\ReportsServerComponent\server_ name\rwserver.conf by commenting out the security tag and removing securityId from the job tags. ■ After making these modifications, the Reports Server must be stopped and restarted using Oracle Enterprise Manager. ■ If Oracle Forms Services is configured to run in Single Sign-On mode, then report requests are sent with the authid provided, based on the Single Sign-On user login. ■ Protected reports and Reports Servers can be registered in Oracle Portal. Table 17–2 lists the possible FormsReports combinations and expected results: 17.6.1 What’s New In This Release? As discussed above, a large number of applications use Oracle Reports in a non-secure mode with Oracle Forms Services. In this mode, the end user need not provide an AUTHID to run a report from Oracle Forms Services; the URL command needs to include only JOBID and the Reports Server name. If unauthorized or malicious users discover the job ID, they can view the job output using GETJOBID through rwservlet to obtain job output that belongs to another user. Prior to 11g Release 1 Table 17–2 Outcome of Forms Reports Integration when Forms is running in SSO Mode or Non-SSO Mode Report Type Registered, Secure Reports Server runs only registered reports Registered, Secure Reports Server runs any reports Non-Secure Reports Server Reports with public access report generated report generated report generated Reports with specific user access report generated report generated report generated Reports with no specific user access report not generated report not generated report generated Non-registered reports report not generated report not generated report generated