[gatein-issues] [JBoss JIRA] Commented: (GTNPORTAL-1141) Problem after logout from a private navigation in a portal

[Esslem GHODBANE (JIRA)]

    [ https://jira.jboss.org/jira/browse/GTNPORTAL-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12529052#action_12529052 ] 

Esslem GHODBANE commented on GTNPORTAL-1141:
--------------------------------------------

I guess that this is problem is due to hard coding the LogoutActionListener.
I find that portal requires going to /public mode as default, it's described in 
org.exoplatform.portal.webui.portal.UIPortalActionListener.LogoutActionListener.execute like that :

public void execute(Event<UIComponent> event) throws Exception
      {
         PortalRequestContext prContext = Util.getPortalRequestContext();
         prContext.getRequest().getSession().invalidate();
         HttpServletRequest request = prContext.getRequest();
         String portalName = URLEncoder.encode(Util.getUIPortal().getName(), "UTF-8");
         String redirect = request.getContextPath() + "/public/" + portalName + "/";
         prContext.getResponse().sendRedirect(redirect);
         prContext.setResponseComplete(true);
      }
So, is there a way to make this redirection dynamically in order to take access permission of the portal and to inject it in this string.
if access-persmission is 'everyone' -> /public
else -> /private

> Problem after logout from a private navigation in a portal
> ----------------------------------------------------------
>
>                 Key: GTNPORTAL-1141
>                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1141
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0-GA
>            Reporter: Esslem GHODBANE
>
> I found a problem which occurred after logout from a private navigation in a portal.
> To reproduce this issue : 
>  * Login to classic portal 
>    * Here we are under  /portal/public/classic/
>  * Edit Portal's Properties
>    * Make classic portal private for navigation
>    * Add permission to *:/platform/users
>  * Logout from this portal
>    * You'll get a warning saying that that page|portal is not found
>    * This is due to that there is a filter that redirect all connection request to a public mode however navigation mode under this portal was changed to private
>  * If you put directly a private URL, like this /portal/private/classic/  you'll got the _login.jsp_ page.
> So, is it a real bug, or I must have more configuration ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira