Great I'm glad that worked. This could be an option on the APF at some
point, but sub-classing is a good solution. It would be great to be able
to add a parameter to URLs that will trigger ACEGI to use the referrer
URL. That way some URLs will return and others won't. Perhaps an
enhancement
Hello.
I'm quite new to Acegi but I think I am getting the hang of it fairly
quickly.
There is one thing though that I am struggling with.
How do I get things like username to be displayed on a web page?
I thought the UserDetails was stored in the Session. But it is really
stored
in an
Charlie,
If you only want the username you can add the filter that exposes the
username as the request.getRemoteUser().
-Scott
Scott Battaglia
Application Developer, Architecture Engineering Team
Enterprise Systems and Services, Rutgers University
v: 732.445.0097 | f: 732.445.5493 | [EMAIL
From a velocity page?
I'm not sure how you get access to the request itself, but start with that...
request.remoteUser
request.userPrincipal.principal.username
You need to add the ContextHolderAwareRequestFilter to your
filterChainProxy for those to work, like Scott had mentioned.
On 8/31/06,
We could wire in a strategy interface for that logic as well.
On 8/31/06, Brian Pontarelli [EMAIL PROTECTED] wrote:
Great I'm glad that worked. This could be an option on the APF at some
point, but sub-classing is a good solution. It would be great to be able
to add a parameter to URLs that
When using the filter, the UserPrincipal is an instance of the Acegi
token ( forgot the classname for some reason).
It depends on what classes you're using I suppose.
Does $request.remoteUser work for you?
On 8/31/06, Charles Harvey III [EMAIL PROTECTED] wrote:
When using VelocityViewServlet all
