Re: [wsrp-wsia] Minutes for 06 March 2003 Meeting

[Michael Freedman <Michael.Freedman@oracle.com>]

JSR 168 requires that resources running in the same portlet application 
have access to the portlet application's session and user identity and 
"role" information.

For sessions, it is anticipated that the JSession cookie will commonly 
be used by JSR 168 applications to maintain the session.   It is 
reasonable to assume that resources, which commonly will have additional 
references back to the application will want to assume such cookie 
support is maintained.

For user information, at the last JSR 168 F2F we discussed how this user 
identity and "role" information can be provided by the portal vs. the 
underlying J2EE security system implying that there be an ability to 
send such information [basically the UserContext] to the portlet 
applications resources.

     -Mike-

Subbu Allamaraju wrote:

> Michael Freedman wrote:
>
>> Rich,
>>   Are you suggesting we defer the discussion of updating the portlet 
>> API to support access/retrieval of resources or are you also 
>> suggesting we defer the discussion of modifying the existing proxy 
>> resource mechanism to allow user context/cookies to be passed when 
>> the resource is invoked?  I hope its not the later as JSR 168 needs 
>> such function -- and asking that the information be carried on the 
>> URL itself suffers not only from the privacy/exposure issue but also 
>> from the long URL issue.
>
>
> Could you clarify why this is a JSR168 requirement?
>
> Subbu
>
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>




----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>