Basically I have two Windows XP environments (with SP2), one is Portal 5.1.0
.3 with LDAP security, and one is a separated WebSphere 5.1 where we install
ed our legacy J2EE applications. Portal server generated LTPA token can be r
ecognized by WebSphere, but
not other way around. In another word, if I log in Portal server first, then
 I could access our applications in the separated WebSphere server without b
eing required to login. However, if I log in our application in the separate
d WebSphere server first,
then I was always prompted the login page at Portal server. By the way, this
 doesn't work even when I used the default Portal theme.

I added some code to check the existence of LTPA cookie at both Portal and W
ebSphere, and the LTPA cookie does be received at both Portal server and Web
Sphere. However, I noticed that the domain and the path of the LTPA cookie a
re null. Not sure if this i
s problem.

Another thing I noticed is that some error messages appear at Portal SystemO
ut.log file, but the error doesn't always appear. It looks like Portal serve
r tries to do something at the response, but not able to. Because the LTPA t
oken comes from the separat
ed WebSphere server, I don't think it's this to cause the problem,

[2/26/07 15:12:48:576 EST] 5ce91e29 SessionContex W SESN0066E: Response 
is already commited to client. Session cookie cannot be set.
[2/26/07 15:12:48:592 EST] 55919e23 SessionContex W SESN0066E: Response 
is already commited to client. Session cookie cannot be set.

I appreciate if somebody can help me out,

[ Post a follow-up to this message ]