Portal Access Control
The scripting operations for access control differ fundamentally from content, layout, or the portlet repository. The reason is that access control data is not transparently cached on the client. To avoid many requests and slow response times for every simple lookup operation, a different programming model is adopted for access control data. The collected access control data for a resource is represented on the client by an object. These objects are explicitly created, locally modified, and written back to the portal. All local modifications become effective when the object is written back.
Two script beans are provided for access control data.
- Access bean, referenced as $Access in a script, is for reading and writing the access control objects.
- PacList bean, referenced as $PacList, provides operations to view and edit access control objects.
See: