PUBLIC - Liferay Portal Community Edition
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-29256

Calling portal services during Kaleo actions causes PrincipalException: PermissionChecker not initialized

    Details

    • Branch Version/s:
      6.1.x, 6.0.x
    • Backported to Branch:
      Committed
    • Fix Priority:
      3
    • Similar Issues:
      Show 5 results 

      Description

      Steps to reproduce the problem:
      1. Go to 'Control Panel' -> 'Custom Fields' and create a custom field for Web Contents
      2. Install Kaleo Web plugin.
      3. Go to 'Control Panel' -> 'Workflow Configuration' and change workflow configuration of the 'Web Content' to any workflow (for example 'Single Approver')
      4. Create or Edit a 'Web Content' and set value for the custom field.
      5. After setting the data for the web content, click on 'Submit for Publication' button.
      6. Switch to user who has permissions to approve.
      7. Go to 'Control Panel' -> 'My Workflow Tasks'
      8. For the task of reviewing the newly submitted web content click on 'Actions' -> 'Assign to Me', 'Actions' -> 'Approve'.
      Result: The web content got approved, but the log shows the following exception:
      ERROR [ExpandoBridgeImpl:507] com.liferay.portal.security.auth.PrincipalException: PermissionChecker not initialized

        Issue Links

          Activity

          Hide
          Matthew Lee (Inactive) added a comment -

          Committed on:
          Portal 6.2.x GIT ID: 41e48149c61bea15b945e3704a5c8b69db507722.

          Show
          Matthew Lee (Inactive) added a comment - Committed on: Portal 6.2.x GIT ID: 41e48149c61bea15b945e3704a5c8b69db507722.
          Hide
          Mark Jin added a comment -

          PASSED Manual Testing following the steps in the description.

          Reproduced on:
          Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2. Plugins: 6.1.20 EE GA2.

          Able to get the error message.

          Fixed on:
          Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: c6c5333ad74ae2843b037d30e671c6cbfb88f2ab. Plugins 6.0.x GIT ID: 5729f8d792791c165ec964b04c1e4c50b552ec1a.
          Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 99d422996293e360a04d47a1cbac8da280ac06b2. Plugins 6.1.x EE GIT ID: 8beb44b28ec7332e4749de4c3d1d319ee83356ac.
          Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e8ab3317581dbeea86bd69bf8965bd898de5b282. Plugins 6.2.x GIT ID: 91c8139b6110c1225391674b7a7f69eb231a2232.

          Unable to get the error message.

          Show
          Mark Jin added a comment - PASSED Manual Testing following the steps in the description. Reproduced on: Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2. Plugins: 6.1.20 EE GA2. Able to get the error message. Fixed on: Tomcat 6.0 + MySQL 5. Portal 6.0.x GIT ID: c6c5333ad74ae2843b037d30e671c6cbfb88f2ab. Plugins 6.0.x GIT ID: 5729f8d792791c165ec964b04c1e4c50b552ec1a. Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 99d422996293e360a04d47a1cbac8da280ac06b2. Plugins 6.1.x EE GIT ID: 8beb44b28ec7332e4749de4c3d1d319ee83356ac. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e8ab3317581dbeea86bd69bf8965bd898de5b282. Plugins 6.2.x GIT ID: 91c8139b6110c1225391674b7a7f69eb231a2232. Unable to get the error message.
          Hide
          Michael Saechang added a comment -

          Thank you Mark for testing. Closing as 'Fixed'.

          Show
          Michael Saechang added a comment - Thank you Mark for testing. Closing as 'Fixed'.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 34 weeks, 2 days ago

                Development

                  Structure Helper Panel