problems with Acegi and WebSphere 6.1

[wpraet]

Just for anyone who wants to know: this issue got fixed in FixPack 6.1.0.11, which was released earlier this week.

[robmoore]

Thanks for the heads-up. Do you happen to know which APAR references the fix in the list (http://tinyurl.com/35r3nt for the entire list).

Rob

[wpraet]

Normally, I'd guess it already would have been fixed in FP6.1.0.9, since this description fits what was happening: http://www-1.ibm.com/support/docview...id=swg1PK31377 (and then you'd obviously still need to set the 'com.ibm.ws.webcontainer.invokeFiltersCompatibilit y' property to true).

But it didn't entirely fix the acegi problems. It did only fix the login part, but not the logout part (and then you'd obviously still need to set the 'com.ibm.ws.webcontainer.invokeFiltersCompatibilit y' property to 'true').

I didn't really find any fix in the 6.1.0.11 FP that matches the logout problem sequence of events, although it is fixed now...

[robmoore]

Thanks for the reply. I'm surprised to hear about the logout issue because I haven't experienced any problems with the logout filter.

[Paul Newport]

Thanks for the reply. I'm surprised to hear about the logout issue because I haven't experienced any problems with the logout filter.

FYI the problem still exists in WAS 6.1 FP 11, at least on the local version of WAS 6.1 that ships with RAD 7, and that is with com.ibm.ws.webcontainer.invokefilterscompatibility set to true

[Paul Newport]

FYI the problem still exists in WAS 6.1 FP 11, at least on the local version of WAS 6.1 that ships with RAD 7, and that is with com.ibm.ws.webcontainer.invokefilterscompatibility set to true

I take that back, it all works fine on this level.