"gaopeng_victor" wrote : "mputz" wrote : You don't need the
cookieDomain, as long as you don't have different host names. Have you seen this wiki
on SSO?
| |
http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
|
| Yes, I've seen that wiki. And I've followed that wiki to establish my cluster,
except that I used two PCs instead of one. I've configed the
org.jboss.web.tomcat.tc5.sso.ClusteredSingleSignOn, enabled the IE cookie. Everything is
ok on startup, but when I login on 10.1.16.64, and then visit
http://10.1.16.140/portal,
it shows that I'm not login.
|
| So I try the cookieDomain attribute, but it also don't work.
|
| Is there anything wrong?
I test the cluster with another simple web application, and find the http session can be
replicated sucessfully on one way. That is: I login on node A(host 1) , from jmx-console,
I can see that the session is copied to node B(host 2) successfully, so I can access B
without loginning again by that session; but the reverse test is fail : when I login on
node B with a new session, the replication to A is fail. why?
As to the jboss-portal-ha 2.6, jmx-console show that session replication is also
successful from A to B, failed from B to A. But even A to B replication is ok, when I
access B's portal by the replicated sessionid, it want me to authenticate again. Is
there any thing I need to do with the jboss-portal-ha?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054297#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...