Great. So the problem appears to be identified. Is there a jira tracking this
issue? Do you know the anticipated release date of the next product cycle that
this fix might be included in? Is there CVS or milestone access to this
release so that I can test and give feedback in a more timely
JIRA:
http://jira.jboss.com/jira/browse/JBAS-3096
Scheduled for 4.0.5.CR1 (or 5.0.0.Beta if it comes out first.
Release schedule:
Neither of the above has a scheduled date right now. To monitor:
http://jira.jboss.com/jira/secure/BrowseProject.jspa?id=10030subset=-1
Kind of a pain, but
Brian,
Thanks for your support and JBoss' continued commitment to enterprise quality
middleware.
anonymous wrote :
| The reason #3 above doesn't work is we're not willing to store the
credential info forever. We discard the info 1) if invalidate() is called on
any session associated with
Thanks! You found a bug in the distributed session manager that I'm fixing for
4.0.4.GA. http://jira.jboss.com/jira/browse/JBAS-3085
anonymous wrote :
| This hack works, but only if node1 stays active. In the scenario where
sticky sessions are used and node1 crashes, traffic is sent to
Hey Jim,
Finally got a chance to play with your wars, and things work as I expect -- but
not as you want :(
The issue is that the Principal does not get propagated around the cluster; the
username and password do. Two reasons for this:
1) Principal does not extend Serializable, thus you can't
It's late, the time when I dream up bad hacks.
What if you add a FORM login config block to hello/hello2, but use your
loginredirect.jsp as the login page? I would expect if the user hits hello w/o
a login, loginredirect.jsp would get called, redirecting to main. However, in
the failover
Assuming we start at node1 and then move to node2...
This hack works, but only if node1 stays active. In the scenario where sticky
sessions are used and node1 crashes, traffic is sent to node2, however node2
still lacks the authentication context and forces a login. If someone where in
a
Any news on 2314?
-Jim
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935596#3935596
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3935596
---
This SF.Net email is
Hi Brian,
Finally had the chance to circle back and re-ramp on my clustered project.
This problem is still there. Session information seems to be replicated fine,
but not auth context.
I didn't exactly understand your explanation above. Is auth context not pushed
along with session
First, congrats to you; hope you had a great honeymoon :)
I took another look this morning and saw the problem that eluded me before.
See
http://jira.jboss.com/jira/browse/JBAS-2314
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3898297#3898297
Reply to the
Any luck verifying this defect? I've been away on my honeymoon these past
couple weeks. Let me know if you need any anything else.
Thanks,
Jim
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3898007#3898007
Reply to the post :
Any verification of this? Another person within my organization has been able
to reproduce the problem. It'll be important for us to know:
A) That this is a bug
B) What the timeframe for resolution will be
Thanks,
Jim
View the original post :
Jim,
Sorry for the slow response. If this is important for your organization and
you need someone from JBoss to help get answers on this quickly, you should
contact our support group. Please understand the forums are a form of free
support and don't necessarily get the attention we would
Thanks for the response Brian. I know you're under time pressures.
What you say makes sense. What it feels like JBoss is doing in SSO is that
upon authentication with one app the principal gets propagated to the other
webapp's context and the credentials are cached. Or there is some security
I should be able to run through your test wars in the next day to get an exact
idea of what's going on.
I definitely appreciate your good inputs on this. Getting a test case so
quickly is not the norm with most forum questions :-) .
View the original post :
15 matches
Mail list logo
