[Backend] Investigate how to split resource actions permission creation from the portlet permission

• Type: Spike
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Application Security > Permissions
• Labels: None
• Spike Type: Technical
• Conclusion:
  Hide

  After having a short talk about this with the team we think we need to deal with it. So I have put this to our themes doc to under the Permission Revamp section for later consideration: https://docs.google.com/document/d/1TrUu-MOzdeiGSPO3LCSvcTIw8uX-9lq6miDMfwB6988/edit#heading=h.uuyzmjv8eb3s ; ; We may need to collaborate with the core infrastructure team.

  Show

  After having a short talk about this with the team we think we need to deal with it. So I have put this to our themes doc to under the Permission Revamp section for later consideration: https://docs.google.com/document/d/1TrUu-MOzdeiGSPO3LCSvcTIw8uX-9lq6miDMfwB6988/edit#heading=h.uuyzmjv8eb3s We may need to collaborate with the core infrastructure team.

Currently the resources model permission are created when the portlet is registered, which gets in the way of having a headless api because we need to have a portlet to get the permissions registered. This is not the best in cases when an application wants to use the data from the portal only. Take REST applications or the Headless concept as examples.

https://issues.liferay.com/browse/LRDOCS-6627

Previous work on the issue https://github.com/Preston-Crary/liferay-portal/pull/637