Text Configuration File Configuring and Using Text PDS

14-24 Publishing Reports to the Web with Oracle Reports Services ORACLE_INSTANCE\config\ReportsToolsComponent\ReportsTools ■ For Reports Application in-process Reports Server deployed in Oracle WebLogic Server: DOMAIN_HOMEconfigfmwconfigserversWLS_ REPORTSapplicationsreports_versionconfiguration Example The following example illustrates the contents of xmlpds.conf file: xmlpds xmlns=http:xmlns.oracle.comreportspdsxml xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:xmlns.oracle.comreportspdsxml file:c:\orawinreportsdtdxmlpds.xsd columnInfo columnLength4000columnLength columnInfo xmlpds

14.4 Specifying the encoding of an XML PDS Report

When you create a report against an XML data source, you must ensure that the encoding of the data source and its DTD matches the encoding of Reports Builder. For example, when you create an XML report against a table encoded in a Japanese character set, the group element name is encoded in Japanese. To match the data source, you should encode the groups element name in the DTD in Japanese. The XML and DTD files can be in any encoding that supports Japanese, such as Shift_JIS, EUC-JP, or UTF-8. If you do not match the XML data source and DTD encoding to the Reports Builder encoding, you will see the following error: ERR-063001 xxx.dtd null To avoid this problem, ensure that both the XML data source and DTD for your XML report use the same encoding that you have in the character encoding part of the NLS_ LANG environment variable in effect for your Reports Runtime. For example, if NLS_LANG=JAPANESE_JAPAN.JA16SJIS for your Reports Runtime, then both your XML data source and DTD should use Shift_JIS. Note: The only parameter that can be changes is the columnLength. The default size of the column is 4000 bytes Note: You will not see this error if you use a XML schema instead of a DTD. 15 Securing Oracle Reports Services 15-1 15 Securing Oracle Reports Services The celebrated openness of the Internet brings with it concerns about controlling who has access to what confidential company information. Oracle Reports provides a number of security options that enable you to ensure that the appropriate users are getting important data in a secure fashion. This chapter contains the following sections: ■ Introduction to Oracle Reports Security ■ Out-of-the-Box Behavior ■ Authentication in Oracle Reports ■ Authorization in Oracle Reports ■ End-to-End Security Scenarios ■ Recommended Production Scenario for JPS-Based Security ■ Recommended Production Scenario for Portal-Based Security ■ Managing Users and Security Policies ■ Configuring External Oracle Internet Directory and Reassociating Reports ■ Forms and Reports Security Recommendations ■ Intermediate-level Security for Forms and Reports ■ Database Proxy Authentication ■ Oracle Portal-Based Security for Backward Compatibility ■ Security Interfaces

15.1 Introduction to Oracle Reports Security

This section introduces security features and concepts in Oracle Reports. It also describes the new security features introduced in Oracle Reports 11g Release 1 11.1.1. This section discusses the following topics: ■ Overview ■ What’s New in This Release? ■ Resources Protected ■ Credential Store 15-2 Publishing Reports to the Web with Oracle Reports Services

15.1.1 Overview

Oracle Reports 11g Release 1 11.1.1 uses a standards-based Java EE security model through Oracle Platform Security Services. This provides a flexible, simple to administer security mechanism. It can be used with standalone Oracle Reports install or any Forms-Reports combination. The policy store and the identity store used for authentication and authorization can be standard JAZN-XML based or any LDAP server, including Oracle Internet Directory through JAZN-LDAP, providing flexibility. Oracle Reports 11g Release 1 11.1.1 accomplishes authentication through Single Sign-On, Oracle Internet Directory, Embedded ID Store, and JAZN-XML File-based ID Store. For authorization, Oracle Reports 11g Release 1 11.1.1 supports Oracle Internet Directory, File-based, and Portal-based methods. In prior releases, Reports Server authentication was restricted to use only Oracle Internet Directory. If you want to revert to the security mechanism of prior releases, you can do so in Oracle Enterprise Manager, as described in Section 7.8.1.1, Switching to Oracle Portal Security . If you want to use OracleAS Single Sign-On without implementing data source security or Oracle Portal, refer to Chapter 17, Configuring and Administering OracleAS Single Sign-On . Alternatively, you might have your own application for launching reports with its own login mechanism and usergroup repository, or have your own mechanism for protecting data sources for example, you might choose to use a different LDAP server to store user and group information. In this case, Oracle Reports Services provides interfaces that allow you to integrate it with these non-Oracle components, as described in Section 15.14, Security Interfaces . 15.1.2 What’s New in This Release? Oracle Reports 11g Release 1 11.1.1 uses Oracle Platform Security Services, enabling a new security mechanism that provides the features and functionality described in Table 15–1 a subset of Table 1–1, 11g Functionality vs. 10g Functionality : Note: JAZN-XML is an XML file which is configured by the user to use as an id store andor policy store. Table 15–1 11g Security Features vs. 10g Functionality 11g New Features Equivalent 10g Functionality A standards-based Java EE security model through Oracle Platform Security Services. This provides a flexible, simple to administer security mechanism. For more information, see Section 15.1, Introduction to Oracle Reports Security Reports Server authentication restricted to use only Oracle Internet Directory. Authorization of Reports Server required Oracle Portal-based security model using Portal metadata repository for checking authorization. Oracle Enterprise Manager advanced user interface. Administrators can use Oracle Enterprise Manager to more easily define and manage granular security policies for reports, directories, Web commands, and readwrite access to directories. For more information, see Section 7.8, Securing Oracle Reports Services in Chapter 7, Administering Oracle Reports Services Using Oracle Enterprise Manager Basic UI in Oracle Portal for defining the policies. Hard-coded Web command access to the Oracle Reports seeded roles. Access policies at file report level only, not folder level.