WebSphere Commerce Portal V5.4 Solutions

366 WebSphere Commerce Portal V5.4 Solutions

portletrequest.getClient().getUserAgent(),

new Hashtable());

} catch (Exception e) {

getPortletLog().error("Could not perform WCS Logon", e);

}

}

}

return (HttpClient) obj;

}

private boolean isSSOEnabled(PortletRequest portletrequest) {

// The SSOEnabled flag in not visible from this class, so we

// get it from PortletSettings again

PortletSettings portletSettings = portletrequest.getPortletSettings();

String ssoString = portletSettings.getAttribute("SSOEnabled");

boolean ssoboolean = false;

if (ssoString != null) {

ssoboolean = (new Boolean(ssoString)).booleanValue();

}

return ssoboolean;

}

Known limitations

The limitations of this solution have been identified as follows:

1. All WebSphere Commerce user IDs used for debugging should match

WebSphere Portal user IDs.

2. All WebSphere Commerce user passwords should be the same and match

the password defined in WCSLogon.properties file in the WebSphere Portal

machine.

3. All portlets should have the SSOEnabled flag set to either true or false.

Otherwise, results may be unpredictable.

4. All portlets must point to the same WebSphere Commerce machine.

5. The currently implemented code is designed for use in a development

environment only, and has several security vulnerabilities. With some

modifications it could be made secure for use in production environments

where single sign-on between WebSphere Portal and WebSphere Commerce

systems is not possible.