Hi Ken, Thanks for posting back and sorry for the delay in answer... You asked about the default security-related behavior in Cactus 1.5.
There are none. There's no security behavior active when you use cactus. Also, AFAIK, nothing was changed from Cactus 1.4.1 except maybe the addition of form-based authentication but this has not changed anything in the architecture. Instead of calling new BasicAuthentication(...) in your beginXXX method you can now call new FormAuthentication(...). BTW, do you still have FilterTestCase problems? Thanks -Vincent > -----Original Message----- > From: Flagg, Kenneth BGI SF [mailto:[EMAIL PROTECTED] > Sent: 14 October 2003 21:44 > To: 'Cactus Users List' > Subject: JBoss, Cactus 1.5-b1, and JAAS - problem solved > > Sorry if I've posted a lot of messages to this list, but I was truly > flummoxed. Anyhow, I have fixed my problem, and my solution may be of use > to other Cactus/JBoss users. > > I copied the jboss-web.xml file from samples\servlet\src\conf\jboss3x to > the > META-INF directory of my cactified WAR, and voila! my test case worked. > It > does not appear that this is documented anywhere. I'm assuming that my > woes > have been a result of cactus 1.5's new authentication features. I'm using > custom form-based auth on my site and therefore have not utilized nor > configured simple HTTP auth or JAAS. > > Anyhow, I hope this is of help to other JBoss/Cactus users who find > themselves in the same boat. > > Thanks, > Ken Flagg > > p.s. What is the default security-related behavior for Cactus 1.5? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
