-
1. Re: No Default Context after failed login
febbraro May 22, 2003 1:52 PM (in response to febbraro)One thing I have figured out was that the behaviour changed from version 3.0.6 to 3.0.7.
It worked the way I wanted in 3.0.6, in 3.0.7 something changed and I can't determine what that is yet. Only thing I can see in the release notes that may be involved is "Allow dispatch to j_security_check"
The broken behaviour is also around in 3.2.1
Thanks for any help,
Frank -
2. Re: No Default Context after failed login
juhalindfors May 24, 2003 3:21 AM (in response to febbraro)If you figure it out, I'd like to know too ;-)
-
3. Re: No Default Context after failed login
andyjeff Jun 7, 2003 10:45 AM (in response to febbraro)Any update on this ?
It is a bit of a stopper on releasing anything for Jboss since it exists in both 3.0.7 and 3.2.1 (whereas, as the original poster mentioned was fine in all up to 3.0.6). It appears that JBoss is 'losing' the Default Context somewhere in the JAAS authenticate process with a failure. -
4. Re: No Default Context after failed login
andyjeff Jun 7, 2003 10:50 AM (in response to febbraro)I'll answer my question ... upon searching down the bugs on Sourceforge, it appears it is (was) a bug in Jetty (was fixed by Greg Wilkins) and will be merged back into JBoss soon. I'll maybe give the JBoss-Tomcat bundle a go since is supposedly fine there.
-
5. Re: No Default Context after failed login
pgmjsd Jun 8, 2003 9:13 PM (in response to febbraro)I've been having this same issue. Any news on when it will be fixed? I'm using JBoss 3.0.6.
-
6. Re: No Default Context after failed login
andyjeff Jun 19, 2003 6:36 AM (in response to febbraro)Fixed in JBoss 3.0.8.
-
7. Re: No Default Context after failed login
tsangcn Jul 11, 2003 3:57 AM (in response to febbraro)Will this be fixed in JBoss 3.2.1? I don't want to fall back to 3.0.8
Thanks