Click the Preferences sub tab and you should see a page similar to the one in

Configuring and Administering OracleAS Single Sign-On 17-13

7. Click Submit. Your resource type is created and you can now reference it in the

data_source_type portion of the SSOCONN value.

17.3.4 Connecting to Oracle Internet Directory

As described in Chapter 15, Securing Oracle Reports Services , Oracle Reports Services must connect to Oracle Internet Directory to verify user privileges and obtain existing data source connection information. In connecting to Oracle Internet Directory, you must consider: ■ Choosing the Connecting Entity for Oracle Internet Directory ■ Choosing the Oracle Internet Directory Instance Connection String Format Defines how Oracle Reports Services should construct the connection string using the values stored in Oracle Internet Directory for the resource. For example: for the Oracle database or a JDBC data source your connection string format might be: orclUserIDAttributeorclPasswordAttribute orclFlexAttribute1 This string indicates that the user name is followed by a slash, the password, an at sign , and then additional attribute 1 for example, for the TNS name of the database. A connection string that adheres to this format would look similar to this one: scotttigerdb1 User NameID Field Name Is the display name of the user name field that contains the value for orclUserIDAttribute. The display name appears on the Create Resource page Figure 17–3 next to the field for orclUserIDAttribute. Typically, you would enter something like Username or User Name for this display name. Password Field Name Is the display name of the password field that contains the value for orclPasswordAttribute. The display name appears on the Create Resource page Figure 17–3 next to the field for orclPasswordAttribute. Typically, you would enter something like Password or password for this display name. Additional Field 1-3 Is the display name of the additional fields, which contain the values of orclFlexAttribute1, orclFlexAttribute2, and orclFlexAttribute3. You must specify these fields for whatever values your connection string requires beyond user name and password. For example, you might use one of them to contain a server or domain name.The display name appears on the Create Resource page Figure 17–3 next to the field for orclFlexAttribute1, orclFlexAttribute2, or orclFlexAttribute3. Typically, you would enter something descriptive of the fields contents, such as Server or Domain, for this display name. See Also: Section 17.3.3.1, SSOCONN . Table 17–1 Cont. Create Resource Type Properties Property Description 17-14 Publishing Reports to the Web with Oracle Reports Services

17.3.4.1 Choosing the Connecting Entity for Oracle Internet Directory

When Oracle Reports Services connects to Oracle Internet Directory, it does so as an application entity. By default, each Oracle Reports Services application entity is unique to its Oracle Fusion Middleware installation. Every Reports Server started from the same Oracle Fusion Middleware installation that is, ORACLE_HOME uses the same application entity to connect to Oracle Internet Directory. This setup ensures that each Reports Server can only access information in Oracle Internet Directory that is relevant to its instance of Oracle Fusion Middleware. For example, suppose you have two instances of Oracle Fusion Middleware, one for your Finance group and one for your Human Resources group. A Reports Server from the Finance groups Oracle Fusion Middleware instance would be prevented from accessing information relevant only to the Human Resources group, and vice versa. Thus, information stored in Oracle Internet Directory is more secure by default. In previous releases of Oracle Reports Services, all Reports Servers connected to Oracle Internet Directory as the same application entity. As a result, it was not possible to restrict a Reports Servers access to information in Oracle Internet Directory. To revert to the less restrictive security mode, refer to the Oracle Reports Services chapter of the Oracle Fusion Middleware Release Notes.

17.3.4.2 Choosing the Oracle Internet Directory Instance

By default, the Reports Server is configured to use the Oracle Internet Directory instance installed with Oracle Fusion Middleware. If you are building your system anew, this arrangement is fine. However, if you have an existing Oracle Internet Directory instance that you want to use for the Reports Server, you have to make some adjustments to your configuration. Changing Oracle Internet Directory instances must be done as part of a complete change of your Oracle Fusion Middleware middle tier. For more information about this process, refer to the chapter on reconfiguring Application Server instances in the Oracle Fusion Middleware Administrators Guide.

17.4 Choosing the Connecting Entity for Oracle Internet Directory

You can merge several application entities so that the Reports Servers installed in separate ORACLE_HOMEs can share available SSOCONN resources. To achieve this merge, you must execute an LDIF file with the ldapmodify command. The LDIF file should contain the following: dn: dn of the group representing the logical grouping of all report instances changetype: modify add: uniquemember uniquemember: dn of the Reports Application Entity where: dn of the group representing the logical grouping of all report instances is cn=Virtual Application Group, orclApplicationCommonName=reports_application_ entity_name, cn=Reports, cn=Products, cn=OracleContext dn of the Reports Application Entity is orclApplicationCommonName=reports_application_entity_name, cn=Reports, cn=Products, cn=OracleContext reports_application_entity_name is in the format reportsApp_hostname_GUID. For example, reportsApp_serv1.us.oracle.com_C7543D42A9E26726E034080020A46EE