|
Problem(Abstract) |
Portal server makes a http request to commerce server but
an error is obtained on commerce server that it is unable to parse ltpa
token. |
|
|
|
Cause |
Portal server makes a http request to a commerce server.
Both portal and commerce servers are in different cells. The sso domain
and security realm are same for both portal and commerce servers. The
following error is seen in logs:
[7/10/06 15:45:01:387 EDT] 2fa2de07 WC_SERVER d
com.ibm.commerce.browseradapter.AbstractHttpSessionContext
handleSingleSignOn The LtpaToken value is <value>
[7/10/06 15:45:01:389 EDT] 2fa2de07 WC_SERVER d
com.ibm.commerce.browseradapter.AbstractHttpSessionContext
handleSingleSignOn Cookie value is <value>
[7/10/06 15:45:02:055 EDT] 2fa2de07 JaasLoginHelp A SECJ0222E: An
unexpected exception occurred when trying to create a LoginContext. The
LoginModule alias is system.DEFAULT and the exception is .
[7/10/06 15:45:02:121 EDT] 2fa2de07 SystemErr R
ERROR:com.ibm.commerce.util.SecurityHelper login failed with exception:
Token is null.
[7/10/06 15:45:02:121 EDT] 2fa2de07 SystemErr R
ERROR:com.ibm.commerce.util.SecurityHelper Unable to get accessid from
public or private credentials.
[7/10/06 15:45:02:124 EDT] 2fa2de07 WC_SERVER d
com.ibm.commerce.util.SecurityHelper login Using accessid : null
[7/10/06 15:45:02:126 EDT] 2fa2de07 WC_SERVER d
com.ibm.commerce.browseradapter.AbstractHttpSessionContext
handleSingleSignOn Unable to decode LTPA token |
|
|
Resolving the
problem |
Looking at the security.xml files for portal and commerce
it is noticed that the ltpa token values for private, public and shared
keys are different. However, they need to be same. To resolve the issue
export the ltpa token from portal server and then import it into the
commerce server. More information on this can be obtained at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_ltpa.html |
|
|