[ http://jira.jboss.com/jira/browse/JBPORTAL-203?page=history ]
Julien Viet resolved JBPORTAL-203:
----------------------------------
Resolution: Done
> Change portal URL style to play nice with https and servlet container
> authentication
> ------------------------------------------------------------------------------------
>
> Key: JBPORTAL-203
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-203
> Project: JBoss Portal
> Type: Task
> Components: Portal Core
> Versions: 2.0 Beta, 2.0 Final
> Reporter: Julien Viet
> Assignee: Julien Viet
> Priority: Critical
> Fix For: 2.0 Beta, 2.0 Final
>
>
> The previous scheme for URL was using a trick to keep the authenticated user
> identity under a non protected URL.
> The new scheme uses the technique :
> the portal servlet is mapped under
> - /*
> - /auth/*
> - /sec/*
> - /secauth/*
> each entry provide a different semantic. The first one is for regular users,
> the second one for authenticated users and the 2 last are same except it
> requires https (using user data constraint to confidential).
> The cms content is relocatable, i.e, /a and /auth/a will display the same
> content.
> Also now all the portal default portlet are in a different war than the
> server itself in order to allow mapping such as /*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
