portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-204) PLT.7.1.2 Portlet URL securit y not implemented and absolute URL rendering
Date Wed, 08 Jun 2005 12:51:16 GMT
    [ http://issues.apache.org/jira/browse/JS2-204?page=comments#action_12313035 ] 

Ate Douma commented on JS2-204:

I'm very sorry to report that I've lost the changes I already made for this issue after my
laptop crashed a few months ago.
I've been looking through all my backups but alas, I have been unable to recover it.

This has now to be redone... (for which I currently don't have the time yet)

> PLT.7.1.2 Portlet URL securit y not implemented and absolute URL rendering
> --------------------------------------------------------------------------
>          Key: JS2-204
>          URL: http://issues.apache.org/jira/browse/JS2-204
>      Project: Jetspeed 2
>         Type: Bug
>   Components: ContentServer, Profiling/Portal Navigation, Container
>     Versions: 2.0-dev/cvs
>     Reporter: Ate Douma
>     Assignee: Ate Douma
>      Fix For: 2.0-M2, 2.0-dev/cvs

> PLT.7.1.2 PortletURL security
> -----------------------------
> The PortalURL doesn't yet honor a request for the explicit generation of secure or non-secure
PortletURLs as required by the Portlet Specification.
> Whatever the setting, a non-secure url is always generated.
> I will implement this requirement using the same solution as provided by Jeremy Boyes
for the Pluto PortalDriver.
> See: http://issues.apache.org/jira/browse/PLUTO-82.
> This solution will use two different Servlet Mappings in web.xml for the JetspeedServlet:
a non-secure (what we have now already: /portal/*) and a secure (/secure/portal/*).
> For the secure mapping a security-constraint with transport-garantee CONFIDENTIAL will
be defined, effectively securing any access through this mapping.
> These mappings are, and also need be, defined in WEB-INF/conf/jetspeed.properties too.
> The AbstractPortalURL will read these properties to determine which path to use for secure
and non-secure PortletURLs.
> Note, these paths will *only* be used when a secure url must be generated while the current
request is not, or visa versa.
> This means, other mappings can still be used (we have also a /jetspeed/* mapping defined
although I don't know why or if it is needed anymore) as long as there isn't a switch from
secure to non-secure or visa versa.
> Absolute URL Rendering
> ----------------------
> Another problem the above solution will partly solve is the current absolute URL rendering
(including the Scheme, ServerName and Portnummer in an URL) which poses problems with Proxy
configurations as has been recently been reported on the list by Scott Heaberlin.
> By using different mappings for the secure and non-secure access we don't need to prefix
the urls with a HTTP:// or HTTPS:// scheme anymore.
> I will also remove the Scheme, Servername and Portnummer encoding in url generation as
currently is done by the JetspeedPowerTool, JetspeedVelocityViewServlet and the ContentLocatingRequestWrapper
of the ContentServer.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

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

View raw message