Database Changes After Adding Service Access Policy
Created: 3 February 2025 Modified:What data changes occur when adding a new Service Access Policy. Created new Rock Service Access Policy. Service Access Policies provide an additional layer of security to prevent unauthorized access to remote services. This information was added by administrator user Test Test with email test@test.com. Keep in mind that Liferay doesn’t enforce referential integrity in the database. Instead it is “enforced” in the code.
Many tables have columns classNameId and classPK. These act as a psuedo foreign key to the ClassName_ table. The ClassName_ table basically references Java classes. These Java classes have associated database tables. ClassPK contains an identifier that references a row in the table. This seems to be used to add levels of abstraction for second order relationships.
In the case of ResourcePermission table is name and primKey columns that contain the information.
The following tables were modified.
- SAPEntry
- 1 record inserted.
- Primary key is sapEntryId.
- Excerpt of inserted record
-
sapEntryId allowedServiceSignatures defaultSAPEntry name 32486 * 0 Rock_Remote
-
- ResourcePermission
- 1 record inserted.
- Primary key is resourcePermissionId.
- Excerpt of inserted record
-
resourcePermissionId name primKey viewActionId 2924 com.liferay.portal.security.service.access.policy.model.SAPEntry 32486 1
-
Diagram is only showing the relationships most relevant.
Resources
tags: java - liferay ce - liferay - ce - mariadb - fedora - 41 - fedora 41 - linux - service access policy - service - access - policy - 7.4