-
Type:
Bug
-
Status: Verified
-
Resolution: Unresolved
-
Affects Version/s: 7.0.X, 7.1.X, Master
-
Fix Version/s: None
-
Component/s: Application Security > Permissions
-
Fix Priority:4
-
Sprint:AS | Iteration 9, AS | Iteration 10, AS | Iteration 11, AS | Iteration 12, AS | Iteration 13, AS | Iteration 14, AS | Iteration 15, AS | Iteration 16, AS | Iteration 17, AS | Iteration 18, AS | Iteration 19, AS | Iteration 20, AS | Iteration 21
-
Git Pull Request:
Problem description:
When a portlet is made up only of {{MVCAction}}s it doesn't need to depend on other services / components. For example it doesn't depend on *-service module that contributes to portlet resource actions. When such contributing module is redeployed with resource action changes those changes are not reflected in resource permissions.
Steps to reproduce:
- Stop portal if running
- Clean portal database
- Comment out resource.actions.configs in oauth2-provider-service/portlet.properties
- Build and deploy oauth2-provider-service module
- Start portal
- Go to Control Panel -> OAuth 2 Administration
- Verify there are error logs similar to
com.liferay.portal.kernel.exception.NoSuchResourcePermissionException: {companyId=20100, name=com.liferay.oauth2.provider, primKey=com.liferay.oauth2.provider, scope=4} - Undo changes in oauth2-provider-service/portlet.properties
- Build and deploy oauth2-provider-service module
- Wait for module deployment and visit again Control Panel -> OAuth 2 Administration
Expected result: No error in logs
Actual result: Again the same error log
- is duplicated by
-
OAUTH2-237 OAuth 2 Administration portlet is unavailable
-
- Closed
-
- is related to
-
LRDOCS-6627 Clarify how permissions get added to the Liferay database
-
- Open
-