Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
Custom PermissionChecker in Liferay 7.0
Hello,
I'm trying to implement a custom PermissionChecker in Liferay 7.0.5. I've found other threads in the forum that suggest using an Ext Plugin, together with modifying the 'permissions.checker' portal property, is one way to accomplish this. However, the documentation in Customization with Ext Plugins states "Ext plugins are deprecated for Liferay Portal CE 7.0 and should only be used if absolutely necessary".
Given this warning, is an Ext Plugin still the best solution, or is a better option now available?
Thank you,
-Jake
I'm trying to implement a custom PermissionChecker in Liferay 7.0.5. I've found other threads in the forum that suggest using an Ext Plugin, together with modifying the 'permissions.checker' portal property, is one way to accomplish this. However, the documentation in Customization with Ext Plugins states "Ext plugins are deprecated for Liferay Portal CE 7.0 and should only be used if absolutely necessary".
Given this warning, is an Ext Plugin still the best solution, or is a better option now available?
Thank you,
-Jake
Hi, What kind of customization you want to do in permissionchecker impl ?
Hi Mohammed,
We are creating multiple sites using the same site template. However, we'd like to be able to set different permissions per site, so, for instance, one site could have some assets viewable by guests, while another other site is entirely private.
We were thinking that extending the PermissionChecker would allow us to manage permissions broadly across these sites, without needing to individually set resource permissions for individual assets in each site. Each site would have its own data (created via service builder) to define what permissions scheme is in place, and our new PermissionChecker would then enforce these rules. (Permission checks for any assets not belonging to one of these sites would fall back to the default PermissionChecker methods.)
Thanks,
-Jake
We are creating multiple sites using the same site template. However, we'd like to be able to set different permissions per site, so, for instance, one site could have some assets viewable by guests, while another other site is entirely private.
We were thinking that extending the PermissionChecker would allow us to manage permissions broadly across these sites, without needing to individually set resource permissions for individual assets in each site. Each site would have its own data (created via service builder) to define what permissions scheme is in place, and our new PermissionChecker would then enforce these rules. (Permission checks for any assets not belonging to one of these sites would fall back to the default PermissionChecker methods.)
Thanks,
-Jake