StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16900892
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-03T15:56:23.513
FavoriteCount
0
LastActivityDate
2013-06-03T15:56:23.513
LastEditDate
LastEditorUserId
0
OwnerUserId
230055
ParentId
16821237
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I found one alternative I hadn't considered before: using the Day CQ ACL Setup Service. It is mentioned at <a href="http://dev.day.com/docs/en/cq/5-5/developing/security_model_changes.html" rel="nofollow">http://dev.day.com/docs/en/cq/5-5/developing/security_model_changes.html</a>. AclSetupService allows one to add permission to a single path or a given user/group. This will be applied on each restart of CQ to guaranteed a certain permission state within CQ. For example, "allow;inherit;everyone;/" prevent everyone from accessing CQ (i.e. it forces all users to login first). As noted in the description of AclSetupService, you will need the following pattern per entry: ( "allow" | "deny" ) ";" ( privileges | "inherit" ) ";" principal ";" path <ol> <li>Choose either "allow" or "deny" for the first part.</li> <li>Next enter one of the privilege below or set it to inherit permission from ancestor.</li> <li>Then enter a single user/group.</li> <li>Finally enter a single path to apply the permission to.</li> </ol> Using this will replace permission set within the repository when you restart CQ. These could be scripted by using the process outlined <a href="http://dev.day.com/docs/en/cq/current/deploying/configuring_osgi.html#OSGi%20Configuration%20in%20the%20Repository" rel="nofollow">here</a> and <a href="http://dev.day.com/docs/en/cq/current/deploying/configure_runmodes.html" rel="nofollow">here</a>. Privileges can be: jcr:read rep:write jcr:all crx:replicate imp:setComplete jcr:addChildNodes jcr:lifecycleManagement jcr:lockManagement jcr:modifyAccessControl jcr:modifyProperties jcr:namespaceManagement jcr:nodeTypeDefinitionManagement jcr:nodeTypeManagement jcr:readAccessControl jcr:removeChildNodes jcr:removeNode jcr:retentionManagement jcr:versionManagement jcr:workspaceManagement jcr:write rep:privilegeManagement 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I automate applying permissions for a JCR node?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USShawn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I automate applying permissions for a JCR node?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.