Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-59163

As a plugin developer I want to declare Service Access Policy entry to be used for non-authenticated users



      Currently there is only one DEFAULT_APP entry that is applied to every request, including non-authenticated.

      When a plugin needs to declare public services, i.e. services accessible by non-authenticated users, the plugin needs to update the DEFAULT_APP entry and add the services. This will happen probably during plugin initialization when plugin recognizes the services are missing in DEFAULT_APP policy.

      Portal administrator may later change DEFAULT_APP and remove some of the newly declared public services, which can cause conflict and unknown behavior during plugin initialization.

      Goal of this story is to allow to define multiple "default" policies so that each plugin can declare own "default" policy. This policy can be than changed or disabled by portal administrator, consequently plugin can still verify the policy exist and there is no need to redefine / update it.


          Issue Links

          There are no Sub-Tasks for this issue.



              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:


                  Version Package
                  7.0.0 Alpha 2