Acegi should be oblivious to the fact that you are using Wicket, so that shouldn't make any difference.
If your wicket filter is placed before the Acegi one in your web.xml then you will have problems if you try to access the security context when wicket decides to handle the request. Likewise (as someone already pointed out) if your Acegi filter stack isn't applied to all the requests. Otherwise the context will always be populated by HttpSessionContextIntegrationFilter. Ian Godman wrote: > The fix I came up with was to get the Authentication from my session class. > > Ian > > ----- Original Message ---- > From: Thies Edeling <[EMAIL PROTECTED]> > To: users@wicket.apache.org > Sent: Tuesday, 18 September, 2007 11:19:20 PM > Subject: Re: Acegi (Spring Security) > > Did you manage to fix this ? I have the exact same symptom, user > authenticates fine > (org.acegisecurity.event.authentication.LoggerListener - Authentication > event AuthenticationSuccessEvent: thies; details: null) but > authentication is not set in the context. > > Thies > > Ian Godman wrote: > -- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
