Test the Ajax proxy configuration for Connections portlets
Test the configuration of the application-specific Ajax proxy to manage authentication for the Connections portlets.
IBM Connections portlets now use an application-specific Ajax proxy as the mechanism for forwarding security headers and cookies with each REST service call to authenticate the request with the Connections server. The proxy is configured as part of the installation process. Use the following test URLs to verify the application-specific proxy configuration is working.
If we are in an SSO environment, first open a new browser window and log in to Portal as a Connections user.
If we have a web server configured for Portal as well as Connections, use:
http://WP_Server/wps/CONNECTIONS_PORTLETS_CONTEXT_ROOT/proxy/https/CONNECTIONS_SERVER_BASE_URL/profiles/atom/profileService.do
For example...
http://webhost/wps/PA_icWEFPtlts/proxy/https/myconnectionswebserver/profiles/atom/profileService.do
If we have a web server configured for Connections but not for Portal, use:
http://WP_Server:Port/wps/CONNECTIONS_PORTLETS_CONTEXT_ROOT/proxy/https/CONNECTIONS_SERVER_BASE_URL/profiles/atom/profileService.do
For example...
http://portalhost:10039/wps/PA_icWEFPtlts/proxy/https/myconnectionswebserver/profiles/atom/profileService.do
If we do not have web servers that are configured for either Portal or Connections, use:
http://WP_Server:Port/wps/CONNECTIONS_PORTLETS_CONTEXT_ROOT/proxy/https/CONNECTIONS_SERVER_BASE_URL:port/profiles/atom/profileService.do
For example...
http://portalhost:10039/wps/PA_icWEFPtlts/proxy/https/myconnectionsserver:9444/profiles/atom/profileService.do
In an SSO environment:
- If we are prompted to save or open a document or a feed renders in the browser, then the proxy is properly configured.
- If we are prompted to enter a user name and password, then the proxy is properly configured but SSO is not enabled.
- If we receive a 403 error in response, then the proxy is not properly configured.
- If we receive a 500 or any other response code, the proxy was properly configured but something else is not working.
In a non-SSO environment, enter the user name and password of a Connections user...
- If we are prompted to save or open a document or a feed renders in the browser, then the proxy is properly configured
- If we receive a 403 error in response, then the proxy is not properly configured.
- If we receive a 500 or any other response code, the proxy was properly configured but something else is not working.
Parent topic:
Deploy the Connections Portlets