You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Joel Charlesworth (JIRA)" <ta...@jakarta.apache.org> on 2005/08/05 19:10:35 UTC
[jira] Created: (TAPESTRY-534) ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
----------------------------------------------------------------------
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
Priority: Minor
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
[jira] Updated: (TAPESTRY-534) WebRequest interface doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()
Posted by "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: WebRequest interface doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal() (was: ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal())
> WebRequest interface 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
[jira] Closed: (TAPESTRY-534) WebRequest interface doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-534?page=all ]
Howard M. Lewis Ship closed TAPESTRY-534:
-----------------------------------------
Fix Version: 4.0
Resolution: Fixed
> WebRequest interface 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
[jira] Assigned: (TAPESTRY-534) ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-534?page=all ]
Howard M. Lewis Ship reassigned TAPESTRY-534:
---------------------------------------------
Assign To: Howard M. Lewis Ship
> ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
> ---------------------------------------------------------------------
>
> 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
>
> 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
[jira] Updated: (TAPESTRY-534) ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrinciple()
Posted by "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 getUserPrinciple() (was: ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser())
> ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrinciple()
> --------------------------------------------------------------------------------------
>
> 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
[jira] Updated: (TAPESTRY-534) ServletWebRequest doesn't expose getRemoteUser(), isUserInRole() or getUserPrincipal()
Posted by "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
[jira] Commented: (TAPESTRY-534) ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-534?page=comments#action_12317852 ]
Howard M. Lewis Ship commented on TAPESTRY-534:
-----------------------------------------------
I'm willing to add any method that's common to both HttpServletRequest and PortletRequest. I'll add the following:
public String getRemoteUser ();
public Principal getUserPrincipal ();
public boolean isUserInRole (String role);
> ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
> ---------------------------------------------------------------------
>
> 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
>
> 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
[jira] Commented: (TAPESTRY-534) ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
Posted by "Joel Charlesworth (JIRA)" <ta...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/TAPESTRY-534?page=comments#action_12317805 ]
Joel Charlesworth commented on TAPESTRY-534:
--------------------------------------------
Environment: tapestry 4.0-beta-3
(sorry, first issue post to JIRA)
> ServletWebRequest doesn't expose HttpServerletRequest.getRemoteUser()
> ---------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> 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