Vincent, Do you still have the original patch? (I'm pretty sure I do if you don't.) The only issues I remember were that we needed to decide what the best path was for implementing it. The "problem" is that it requires an internal round trip and detecting that scenario was a little painful (more user configuration than I would prefer), but not impossible.
The process was: 1. Make a normal request, automatically inserting JSESSIONID if we have one. 2. We're we redirected? If so, were we redirected to the user-defined login page? 3. If so, we need to log in. Do that. Cache the JSESSIONID that's returned. 4. The response to the login request should be the response from the initial request so make sure it gets routed properly and the rest of the unit test continues as if nothing happened. I guess one issue that was indirectly raised was the issue of keeping state (JSESSIONID) between unit tests. This was a while back during a big philosophical discussion about unit testing and I brought up a point paralleling the one person's desire to keep state with form-based authentication but I don't recall ever seeing a response and I forgot about it until now. So do your feelings on this extend to form-based authentication, or is this a special case? Jason -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 4:07 AM To: 'Cactus Users List' Subject: Jetty integration & Form-based authentication (was FW: Cactus) FYI. I have also committed the Jetty integration thing in CVS and it's working for me! I'll write up a short tutorial soon. If some of you are interested, feel free to ask and I can give quick directions and information. Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: 08 September 2002 09:09 > To: 'nathan phillips' > Subject: RE: Cactus > > Hi Nathan, > > Thank you very much for the compliment. It's great to know I can be of use > to someone! :-). I really like to receive feedback (be it good or bad) but > I don't receive that often ... So, thank you for that! > > WRT Cactus and Jetty, you'll be glad to know that I have finished a very > tight integration with Jetty which allow Cactus tests to be run > transparently from any IDE or any simply Ant junit task. I'll try to > commit the work during this coming week. > > Again that's a special integration, very unlike the Ant scripts that we > currently have for the other application servers. As Jetty is embeddable > it has allowed me to go much further in term of integration! I'm really > excited about the result. > > WRT form-based authentication, Jason Robertson (if I remember correctly) > had posted a patch on the mailing list a long time ago but there were a > few things that needed to be corrected before it could be integrated. I am > currently struggling for time (I'm working on other open source projects > and I'm writing a book, which takes all my time - that's for my night time > of course ;-)). Thus, I'm waiting for someone to step in and submit again > a patch. > > Nathan, can I repost this exchange to the Cactus mailing list. There's > information that will interest others and maybe someone will step in for > the form-based authentication stuff? > > Thanks > -Vincent > > > > -----Original Message----- > > From: nathan phillips [mailto:[EMAIL PROTECTED]] > > Sent: 08 September 2002 02:56 > > To: [EMAIL PROTECTED] > > Subject: Cactus > > > > > > > > Hi Vincent, > > > > I wanted to thank you for doing such a great job with Cactus. I've been > > using it with great success on my current project. I was wondering if > > there > > were any plans for Form based security support and support for Jetty any > > time soon? Thanks again. > > > > Nathan > > > > _________________________________________________________________ > > MSN Photos is the easiest way to share and print your photos: > > http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
