Customize the WSRP resource proxy

The WSRP resource proxy is used by the WSRP Consumer to load resources that are referenced by remote portlets. Depending on your environment, it may be necessary to customize the resource proxy behavior with respect to the following aspects:

• SSL settings for secure connections to remote resources

• LTPA token forwarding for single sign-on scenarios

• Proxy server settings for outbound connections

• Support for relative URLs

• HTTP basic authentication for outbound connections

• HTTP headers that are not forwarded.

• Customize the WSRP resource proxy SSL settings

  The WSRP resource proxy uses one SSL configuration for all secure outbound connections.

• Customize the WSRP resource proxy for LTPA token forwarding

  The WSRP resource proxy can forward single sign-on cookies (LTPA, LTPA2) from the client requests to resources in the same single sign-on domain.

• Customize the WSRP resource proxy for proxy server support

  The WSRP resource proxy supports HTTP proxy servers. It can connect directly to remote resources or to a proxy server that forwards the requests to remote resources.

• Disable support for relative URLs for the WSRP resource proxy

  By default, the WSRP resource proxy serves resources relative to the current resource proxy URI. As this may impose a security risk, you can switch off the support for relative URLs.

• Customize the WSRP resource proxy for basic authentication

  You can customize the WSRP resource proxy for HTTP basic authentication.

• Customize the WSRP resource proxy HTTP header forwarding behavior

  By default, the WSRP resource proxy forwards all HTTP headers from the client request except for the host header and cookie headers. You can define further headers that you do not want to be forwarded.

Parent topic:

Customize the WSRP configuration of your Consumer portal

Related tasks

Parallel portlet rendering with WSRP
Switching off the caching of Producer service descriptions
Customize Client Cookie Forwarding

---