Re: [wsrp] Rewriting redirect URLs

[Stefan Hepper <sthepper@hursley.ibm.com>]

I think that this is something quite often needed if you have external 
authentication systems.

Maybe another alternative to satisfy this usecase would be to allow 
returning an updatedResponse together with the redirect url. That way 
the consumer could construct the render url with the returned render 
parameters and portlet mode/window state itself and set if e.g. as HTTP 
location header. The drawback of this solution would be that 
updatedResponse contains much more than we would want to allow and thus 
would be ignored (markup, events, ...).

Stefan

Subbu Allamaraju wrote:
> I would like to bring the question of rewriting redirect URLs again.
> 
> Per the spec, redirect URLs are required to be absolute, and there is no 
> requirement for the consumer to rewrite redirect URLs.
> 
> The need for absolute URLs makes sense since the consumer does not know 
> how to redirect to the producer over http. It only knows about the SOAP 
> end point.
> 
> However, there is still a use case that can benefit from rewriting 
> redirect URLs. This use case was discussed during the JSR286 meeting, 
> and I would like to see what the TC thinks about this. Here it is.
> 
> During pbia, a portlet would like to redirect the client to an external 
> URL. In that URL, the portlet encodes an action/render URL that the 
> external site will redirect to, once the user exits the external 
> application.
> 
> In this use case, the redirect URL might look like
> 
> "http://blah.com/blah/blah?returnTo=wsrp_rewrite?wsrp-urlType=render&.../wsrp_rewrite"; 
> 
> 
> The portlet may also want to embed portlet's context and state in this URL.
> 
> When consumer rewriting is enabled, it will have to use rewrite tokens 
> to create this return URL.
> 
> For this use case to work, the redirect URL needs to rewritten by the 
> consumer.
> 
> Any comments on this use case?
> 
> Subbu
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
>