SpNego is LGPL so you should be able to use it. If it was purely GPL, even I wouldn't be able to use it.
Oh, if you're going to do what I did with the SpnegoHttpFilter class, (on the doFilter method) you'd need to assign the principal directly onto the request before moving onto the next valve. I have no idea why when turning it into a valve, the request object doesn't get updated with the principal. The other nasty bit I have to do with this, is now that the request object gets populated with the user principal I need to have some httprequest retrieval on my EJB web service. I wish I could do this cleanly (without my EJB code having http code), but that's probably one of my "things to improve-on" later. Thanks for the help! David Blevins-2 wrote: > > On Jul 22, 2011, at 12:28 AM, rnieto wrote: > > That's really excellent!! I'm also under a deadline (speaking at OSCON on > Monday), but about to dig out the 3.1.4 code and prose a hack to get you a > hook into the code so you could extend that part of the system. > > The valve approach is better :) Perhaps not as cool as filters, but they > get the job done. > > Spnego appears to be GPL so we couldn't take it anyway. But you could > certainly contribute it back to Spnego. > > Anyway, wonderful to hear it's working. We'll definitely fix up the WS > context thing on our end. The WS Servlets we create should go right into > the app where they came from. > > -David > -- View this message in context: http://openejb.979440.n4.nabble.com/Tomcat-Servlet-Filters-or-Valves-and-OpenEJB-tp3680204p3686321.html Sent from the OpenEJB User mailing list archive at Nabble.com.
