Liferay 7 Portlet Permission Issue

[Sai Mohan Gadamsetty, geändert vor 7 Jahren.]

Hi,

With Liferay 7 there is an issue while deals with portlet permissions, please refer the issue #LPS-28909 if we keep permissions.check.guest.enabled=false

then we are facing problem during user login time

• Displaying error as "You don't have Permission to View this Page"
• But user landed page has permission to Guest and other roles as well, actually its generating below url
• http://localhost:8080/web/extranet/home?p_p_id=com_liferay_login_web_portlet_LoginPortlet&p_p_lifecycle=1&p_p_state=exclusive&p_p_mode=view&_com_liferay_login_web_portlet_LoginPortlet_javax.portlet.action=%2Flogin%2Flogin&_com_liferay_login_web_portlet_LoginPortlet_mvcRenderCommandName=%2Flogin%2Flogin

can we find any workaround on this issue.

And setting up above property as false is causing more problems with in other ares as well. Enabling guest view for portlets which are deployed on private pages doesn't make any sense and its against Liferay private page spefication.

Could any one help on this please.

[David H Nebinger, geändert vor 7 Jahren.]

Right but this is "works as expected".

Giving all users guest permissions is a shortcut for not having to manually specify permissions on everything.

If something is guest visible, then when all users have guest permissions then guests can view it too.

However, if you set permission.check.guest.enabled=false, you are indicating that you want to manually control permissions to absolutely everything in the portal.

You are saying you are going to manage page permissions, portlet permissions, content permissions, etc explicitly on absolutely everything.

This is "as expected". Anything you're seeing about not having permissions means the thing you want to see has not been specifically permissioned to give you access as a user.

[Sai Mohan Gadamsetty, geändert vor 7 Jahren.]

Hi David,

Thanks for your quick reply.

I understood your explanation on this. But this is strange only priavate page portlets having this concern where page(s) and content permissions are not having this issue.