Ben,
Can Ageci set the correct remote user on the request object on successful authentication?

ie
Code:
request.getRemoteUser()
should transparently return

Code:
((net.sf.acegisecurity.providers.dao.User) auth.getPrincipal()).getUsername()
Some third party libraries/filters like Clickstream use the standard HttpServletRequest API call getRemoteUser() to determine the remote user. It would be nice if the same API call works even when using Acegi authentication as it would make the Acegi authentication more spec compliant or more aligned with the Servlet Web Container authentication.

I do see the difficulty implementing this since the HttpServletRequest interface does not have a setRemoteUser(..) and neither does Weblogic's' implementation of this interface however maybe you can come up with a solution like wrapping the container HttpServletRequest with a proxy in the Agegi filter.


Thanks,
Sanjiv