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 Security
-> 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 Security
-> Global security
-> Web and SIP security
-> General settings
, and select Use available authentication data when an unprotected URI is accessed
Parent topic: Configuring the HTTP proxy for AJAX applications: imc3