WindowsPrincipal BUG: It needs to implement Serializable

Sep 22, 2010 at 8:28 PM

Hi dblock!

We were forced to create our own version of NegotiateSecurityFilter and WindowsPrincipal, because HttpSession#setAttribute requires WindowsPrincipal to be serializable.

The fix on WAFFLE code will look like this:

public class WindowsPrincipal implements Serializable 

No changes needed to NegotiateSecurityFilter. Our custom version did need the change of course, because we have to use a subclass of WindowsPrincipal. That subclass implements Serializable, and must be coded into our special version of NegotiateSecurityFilter.

After that, WAFFLE 1.3 worked for us. But this fix must be added to WAFFLE itself.

Thanks dblock!

Regards,
thenonhacker

 

Coordinator
Sep 23, 2010 at 2:14 PM

Two people ran into this problem the same day :) Did you guys try some new version of Tomcat? http://waffle.codeplex.com/workitem/9456 was filed and has been resolved (quite a few other changes went in, including other classes that got Serializable, unit tests and some proper equals / hashcode overrides).

Sep 23, 2010 at 2:17 PM

Yes, we are using Tomcat 5.5 with WAFFLE 1.3.

Thanks for fixing! When will you release the next version with the "Serializable" fixes?

Coordinator
Sep 23, 2010 at 2:31 PM
thenonhacker wrote:

Yes, we are using Tomcat 5.5 with WAFFLE 1.3.

Thanks for fixing! When will you release the next version with the "Serializable" fixes?

 I don't have a date plan, sorry. I'll make a 1.4 beta build though quickly.

Sep 23, 2010 at 6:48 PM

I got your 1.4 Beta and got it to work.

Looking forward to the stable version. Thanks dblock!