what is the difference between:
request.getRemoteUser()
and this
public String getLoggedInUserName() {
if (SecurityContextHolder.getContext() != null) {
Authentication auth =
SecurityContextHolder.getContext().getAuthentication();
if (auth != null) {
UserDetails user = ((UserDetails) auth.getPrincipal());
if (user != null) {
return user.getUsername();
}
}
}
return null;
}
i found both off them on the net ...
tibi
tibi wrote:
jep... as i understood it the method was already in.
the request.getRemoteUser works fine
tibi
Matt Raible wrote:
The bug you reference was to add a convenience method to get the
user's username. However, since it's easy enough to get with
request.getRemoteUser(), I didn't add it.
Does this answer your question?
Matt
On 5/8/07, tibi <[EMAIL PROTECTED]> wrote:
i just stumlbed upon this bug report:
http://issues.appfuse.org/browse/APF-650
as i understand it the first user is saying that
the method setCurrentUser should be reneamed to setCurrentUserName
because you are not setting the user but only his or her name.
and the getCurrentUser should be changed to getCurrentUserName etc...
but i think at this moment the methods are gone all to getter right?
and super.getRequest().getRemoteUser() should be used?
tibi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
