What You Should Know About the Oracle WebCenter Pagelet Producer

Managing the Oracle WebCenter Pagelet Producer 24-5 ■ Section 24.4.3, Policy ■ Section 24.4.4, Autologin ■ Section 24.4.5, Headers ■ Section 24.4.6, Pagelets ■ Section 24.4.7, Injectors ■ Section 24.4.8, Parsers

24.4.1 General

On the General page, enter basic information about the resource. 1. Enter a Name for the resource. Enter an optional Description. 2. In the Source URL field, type the URL to the internal web application to be proxied. For example, http:internalServerfoo.

3. By default, the Pagelet Producer attempts to connect to the resource for 30 seconds

before returning an error message. To change this value, enter a new Source Timeout period in seconds.

4. In the Destination URL field, type the URL to be used to access the resource. This

URL must be on the server that hosts the Pagelet Producer. In the Pagelet Producer URL space, you must specify a relative path at which the content must appear.

5. The Pagelet Producer enables URL Rewriting by default. When URL rewriting is

enabled, the Pagelet Producer rewrites URLs in the proxied application that begin with the source URL prefix so that they point to the destination URL prefix. There are two cases in which you should disable URL rewriting: ■ The internal URL prefix and external URL prefix are identical. In this case, the users DNS must resolve the URL to the Pagelet Producer proxy server, and the Pagelet Producer proxy servers DNS must resolve the URL to the internal resource. Because DNS only resolves IP and not port, both servers must listen to the same port. This method is strongly recommended. ■ All links in the application are relative URLs. In this case, the internal URL prefix path and the external URL prefix path must be identical. For example, if the internal URL prefix is http:internal_serverbar the external URL prefix path must be bar or http:proxy_serverbar. To disable transformation, deselect URL Rewriting. 6. To enable Dynamic HTML, choose DHTML Rewriting. This option supports URLs that are not in the original HTML returned from the server, but are added by DHTML. In most cases, this option should be enabled. Note: If you are configuring an ADF Web Application as a resource, the Source URL cannot be any more specific than http:hostname:portnumbercontext-root. 24-6 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

24.4.2 CSP

User and session scope preferences can be shared by more than one pagelet. CSP metadata can be used to specify which session preferences can be set or obtained from the application and which user info preferences will be sent to the application. For example, if you store personally identifiable information such as an employee ID as a user preference, you can control which pagelets have access to this information. By default, the CSP login token is not passed to the proxied resource. To enable this feature, choose Send CSP Login Token. You must also enter the name and type of each of the settings that should be retrieved from the Pagelet Producer.

24.4.3 Policy

The Policy page allows you to limit access to a resource to specific roles within Oracle WebCenter. The J2EE container hosting Pagelet Producer such as Oracle WebLogic Server is responsible for establishing the role memberships associated with the current user. A resource can specify multiple roles on the Policy page, and users will be allowed access if they are a member of any of the specified roles; otherwise they will be directed to a suitable J2EE container delegated authentication page to establish the required credentials. If no roles are entered in the list, anonymous access is allowed, and the resource is termed as an anonymous resource.

24.4.4 Autologin

The Autologin page allows you to provide authentication information for a resource for use by all users who access the resource. The autologin feature allows the Pagelet Producer to supply credentials to applications automatically. The credentials used by the Pagelet Producer to log in to the application can come from: ■ Credential vault: When a user logs into the proxied resource, credentials are stored in the Pagelet Producer credential vault. Subsequent access to that resource is authenticated using the stored credentials. When using vault storage, the key name chosen should be a generic placeholder and should not reflect sensitive information like the actual password. ■ The users LDAP profile: Credentials for specific applications can be stored in the users profile and used by the Pagelet Producer to automatically log the user into proxied applications. ■ Static credentials: The Pagelet Producer resource can be configured with static credentials that are used for every user with access to the resource. The Oracle WebCenter Pagelet Producer can automatically log in to resources through HTML forms and basic authentication. The following sections describe how to configure credential mapping for authentication: ■ Section 24.4.4.1, Form Login, describes how to configure a resource to log in automatically to a resource that prompts for authentication with an HTML form. Note: Pagelets associated with a resource inherit this metadata. Note: The role names entered here must match those created in the Oracle WebLogic Server administrative Console.