[jira] Updated: (TAPESTRY-534) ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()

["Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>]

     [ http://issues.apache.org/jira/browse/TAPESTRY-534?page=all ]

Howard M. Lewis Ship updated TAPESTRY-534:
------------------------------------------

    Summary: ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()  (was: ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrinciple())

> ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()
> --------------------------------------------------------------------------------------
>
>          Key: TAPESTRY-534
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-534
>      Project: Tapestry
>         Type: Improvement
>   Components: Framework
>     Versions: 4.0
>  Environment: n/a
>     Reporter: Joel Charlesworth
>     Assignee: Howard M. Lewis Ship
>     Priority: Minor
>      Fix For: 4.0

>
> Trying to migrate an application based on Tapesty 3.x.
> Currently, the application relies on using IRequestCycle.getRequest() method to call HttpServletRequest.getRemoteUser() to determine if the user is currently authenticated. This is also a quick way to get the username of the user.
> Would it be feasible to expose getRemoteUser() within Tapestry 4's ServletWebRequest wrapper?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org