Contents: Administering Mashup Center : Mashup Center 2.0
This topic describes known issues when configuring the AJAX proxy.
Accessing secured sites and importing certificates
When accessing feeds or widgets from a secured site using the HTTPS protocol, if the certificate is not trusted, the Mashup Center proxy will not be able to access the feed. As a workaround, open the WebSphere Application Server administrative console and click SSL certificate and key management
-> SSL Configurations
-> Key stores and certificates
-> Signer certificates
-> Retrieve from port
to manually import the HTTPS certificate of a remote site before using the AJAX Proxy to access it.
Configuring WebSphere Application Server security settings to use available authentication data when accessing unprotected URIs
In a clustered environment, if you get a 500 error when publishing pages from the mashup builder to the catalog, then open the WebSphere Application Server administrative console, click Secure administration, applications, and infrastructure
-> Web security
-> General settings
, and select Use available authentication data when an unprotected URI is accessed
Published pages have the wrong owner
URL normalization fixes in the proxy recognize semantically identical URLs even though they differ syntactically (normalizing URLs). The Mashup Center fix pack 18.104.22.168 solves this by allowing you to configure the proxy-config.xml file to forward session and LTPA cookies to MashupHub or to a selected URL.
Parent topic: Configuring the HTTP proxy for AJAX applications : Mashup Center 2.0