About BrowserUrlPath Customization Browser URL Customization

Managing Security and User Access 5-63

5.9.1 LoginLogout Customization

The ExtranetLook component can be used to customize user access by suppressing the interface for users who are not authenticated by an Oracle WebLogic Server user store through error and challenge pages issued by the web server. See Oracle Fusion Middleware Developers Guide for Oracle Universal Content Management for details about changing the interface. The ExtranetLook component is installed disabled by default with Oracle Content Server system. To use the component you must enable it with the Advanced Component Manager.

5.9.2 Browser URL Customization

The BrowserUrlPath component provides support for determining URL paths used in certain configurations of the Oracle Content Server system and web servers. This component is installed disabled by default with the Oracle Content Server system. To use this component you must enable it with the Advanced Component Manager. This component is valid for an Oracle Content Server instance deployed on an Oracle WebLogic Server domain and located behind a load balancer. The following topics are discussed in this section: ■ Section 5.9.2.1, About BrowserUrlPath Customization ■ Section 5.9.2.2, Affected Idoc Script Variables and Functions ■ Section 5.9.2.3, Determining the URL Path ■ Section 5.9.2.4, Changing Absolute Full Path Computation ■ Section 5.9.2.5, Changing Administration Path Computation

5.9.2.1 About BrowserUrlPath Customization

The BrowserUrlPath component overrides certain Idoc Script variables and functions, adds computation to certain variables, and provides additional configuration entries for determining URL paths. The BrowserUrlPath component is only supported with Trays and Top Menu layouts for the Oracle Content Server user interface. ■ You can configure a system with different web server front ends. One front end can use HTTP and the other can use HTTPS so that the Oracle Content Server instance can be accessed simultaneously by web sites using HTTP and HTTPS. You then must apply the BrowserUrlPath component to enable the Oracle Content Server instance to handle both types of access. ■ If you are using a load balancer that forwards itself as the HTTP host header, then you must apply the BrowserUrlPath component. BrowserUrlPath configuration variables are located in the UCM_ORACLE_ HOMEucmidccomponents BrowserUrlPathconfig.cfg file. Caution: The BrowserUrlPath component requires extensive configuration using the variables. You may want to back up your configuration before modifying variables 5-64 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server In typical scenarios, the web server will forward to the Oracle Content Server instance two critical pieces of information: ■ HTTP_HOST: The host header that the browser sends, identifying the host as it appears to the user in their browser address bar. ■ SERVER_PORT: The port the browser uses in connecting to the Oracle Content Server instance. The browser-based full address is used for two critical pieces of functionality: 1. Automatic creation of URLs in the side frame of the Trays layout for the Oracle Content Server instance. In particular, the side mini-search requires a prediction of the full URL, not just the relative URL. 2. The secondary URL the xml-http... piece following the PDF URL that does highlighting for PDF documents. Without any additional configuration, the BrowserUrlPath component augments the functionality of certain variables, so if SERVER_PORT has the value 433, then the component assumes the protocol is HTTPS instead of HTTP. Likewise, if SERVER_ PORT does not have the value 433, then the component assumes the browser issued the request using HTTP and not HTTPS. This enhancement allows both a SSL HTTPS and non-SSL web server HTTP to access the same Oracle Content Server instance. This component also has special functionality for WebDAV access. The configuration entry WebDavBaseUrl is augmented so that its usage is dynamic its host and protocol vary using the absolute path rules.

5.9.2.2 Affected Idoc Script Variables and Functions