You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2005/11/02 19:48:55 UTC

[jira] Created: (COCOON-1674) Improved user support for portlets

Improved user support for portlets
----------------------------------

         Key: COCOON-1674
         URL: http://issues.apache.org/jira/browse/COCOON-1674
     Project: Cocoon
        Type: Task
  Components: Blocks: Portal  
    Versions: 2.2-dev (Current SVN)    
    Reporter: Carsten Ziegeler
     Fix For: 2.2-dev (Current SVN)


A portlet has access to the current user via the PortletRequest object (username, principal, isUserInRole). Currently this is just a wrapper for the httprequest. As the portal might use different authentication mechanisms, we have to provide a username etc. in this case as well.
I already started to add factories for own wrappers of the portletrequest objects.

-- 
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


[jira] Closed: (COCOON-1674) Improved user support for portlets

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/COCOON-1674?page=all ]
     
Carsten Ziegeler closed COCOON-1674:
------------------------------------

    Resolution: Fixed

> Improved user support for portlets
> ----------------------------------
>
>          Key: COCOON-1674
>          URL: http://issues.apache.org/jira/browse/COCOON-1674
>      Project: Cocoon
>         Type: Task
>   Components: Blocks: Portal
>     Versions: 2.2-dev (Current SVN)
>     Reporter: Carsten Ziegeler
>     Assignee: Cocoon Developers Team
>      Fix For: 2.2-dev (Current SVN)

>
> A portlet has access to the current user via the PortletRequest object (username, principal, isUserInRole). Currently this is just a wrapper for the httprequest. As the portal might use different authentication mechanisms, we have to provide a username etc. in this case as well.
> I already started to add factories for own wrappers of the portletrequest objects.

-- 
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


[jira] Zugewiesen: (COCOON-1674) Improved user support for portlets

Posted by "Jörg Heinicke (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/COCOON-1674?page=all ]

Jörg Heinicke reassigned COCOON-1674:
-------------------------------------

    Assign To: Cocoon Developers Team

> Improved user support for portlets
> ----------------------------------
>
>          Key: COCOON-1674
>          URL: http://issues.apache.org/jira/browse/COCOON-1674
>      Project: Cocoon
>         Type: Task
>   Components: Blocks: Portal
>     Versions: 2.2-dev (Current SVN)
>     Reporter: Carsten Ziegeler
>     Assignee: Cocoon Developers Team
>      Fix For: 2.2-dev (Current SVN)

>
> A portlet has access to the current user via the PortletRequest object (username, principal, isUserInRole). Currently this is just a wrapper for the httprequest. As the portal might use different authentication mechanisms, we have to provide a username etc. in this case as well.
> I already started to add factories for own wrappers of the portletrequest objects.

-- 
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