Acegi login failure: redirect gets lost in Websphere v6.1

[Luke Taylor]

I believe you have misread the fix version in the supplied link in JIRA issue, it reads 6.1.0.3 which is long passed. I got Acegi login to work under 6.1.0.9 with the suggested web container variable set, but it no longer works under 6.1.0.11.

I meant the workaround that involves creating a file whose name matches the URL you are requesting.

[kantorn]

Yes, I tried it. Maybe I wasn't doing it right, but for me made things much worse.

[daf6265]

Yes, I tried it. Maybe I wasn't doing it right, but for me made things much worse.

For me this works when using 6.1.0.11 + Web Services Feature Pack.

[kantorn]

Cool!
Where can I find Web Services Feature Pack?

[Paul Newport]

Hi!

Is it!?

I get "HTTP 404 Not Found" on a brand new 6.1.0.11 install

When do you get this error ?

I have Acegi/CAS all working fine in WAS 6.1.0.11, and know the pitfalls pretty well. Should be easy enough to sort out.

[Paul Newport]

Cool!
Where can I find Web Services Feature Pack?

Not needed to get WAS/ACEGI/CAS working though :-)

[kantorn]

Should be easy enough to sort out.

I would of course be most grateful for any step-by-step description how you have succeded in getting this work. The suggested solution with a dummy resource in the WAR-file just made my app crash even before the login view was displayed. Hence made things worse.

[daf6265]

Cool!
Where can I find Web Services Feature Pack?

I dont think the Web Services Feature Pack has anything to do with this but you can find it here: http://www-1.ibm.com/support/docview...id=swg27004980

[Paul Newport]

OK, first things first. What are you deploying on ?

Are you running locally with RAD 7 and WAS 6.1 ?

The crucial WAS bug is solved by adding in the property com.ibm.ws.webcontainer.invokefilterscompatibility =true on the web container.

The big source of confusion for me in fixing this was not realizing that when I apply fix packs to RAD 7, it does not apply WAS fixes at the same time to the integrated WAS 6.1 server that comes with RAD 7. You have to patch your local WAS with the full WAS fix packs (which is quite an involved process).

Can you confirm the following:

a) the application is running on at least WAS 6.1.0.11 e.g. WebSphere Platform 6.1 [BASE 6.1.0.11 cf110734.37]

b) the exact URL you are having the 404 on

Can you post the acegi config for your application, and web.xml.

404's for me have always been either:

servlet filter configured wrongly in web.xml
com.ibm.ws.webcontainer.invokefilterscompatibility not set to true
com.ibm.ws.webcontainer.invokefilterscompatibility set to true but WAS not patched to correct level.

[kantorn]

Hi Paul and thanks!
I haven't forgot this one, but it's amazing how quick a working solution establishes itself in an organisation. Tomcat working, and no questions asked.
Until X-mas I probably won't get any opportunity to test your solution, but let me return with proper answers in a couple of days, ok? This is of grat strategic value to us.
Like Terminator, I'll be back!

Happy Holidays if I don't see ya'!