file permissions using iwaccess

Is there a way to run iwaccess set-inheritance for a set of files inside a folder.
set-inheritance accepts a argument vpath which is upto a branch. I need to do it for a branch/WORKAREA/Content/folder/*.*.

This is to set "apply inherit permissions" to every file inside a folder.

Find more posts tagged with

Comments

LooseCannon

No. iwaccess set-inheritance only applies to branches.

One way to propagate permissions is to set the GID on workareas and directories:

workarea_default_perm=2770
directory_default_perm=2770

sridharg

We have our Teamsite on windows and moreover,we have set "inherit permissions" from the Teamsite UI at a branch level and we found many of the files for which the permissions have not been inherited from its parent folders. Thats the reason Im looking out for set-inheritance through a command lin.

Are there any KB articles available for setting GIDs as you specified.

Adam Stoller

We have our Teamsite on windows and moreover,we have set "inherit permissions" from the Teamsite UI at a branch level and we found many of the files for which the permissions have not been inherited from its parent folders. Thats the reason Im looking out for set-inheritance through a command lin.

Are there any KB articles available for setting GIDs as you specified.

I ran into a similar problem on my last project (also on Windows) but we had a bunch of issues during content migration from an old 5.5.2 backing store - so I didn't consider it as necessarily an inherent (no pun intended) problem.

I think it may make a difference when the inheritance property is set and when the content is created.

I ended up making a Perl script that traversed the various branches and fixed each file - it was a quick-and-dirty script which basically ran iwaccess add-windows-permission "$path" -group $group -perm F where

$path

was the vpath to a specific file and

group

was the particular group to set full permissions for on that file.

After you set the access, you need to submit the files again - if the permissions don't hold - then there's an issue with your submit.cfg file.

I'm pretty sure that all subsequently created files will get the right permissions, though I cannot say for sure that I verified that.

LooseCannon

I have no experience with Windows. My experience with set-inheritance and permission propagation is with 6.7.1 SP1 / Red Hat, so take it for what it's worth...

Setting set-inheritance to true on a branch specifies whether the branch inherits from its parent branch (or store *I think*) and NOT whether the branch's permissions are propagated to its workareas, dirs, content, etc.

PROBLEM:
The problem for me was with newly created files and dirs retaining the user's primary group as the sharing group instead of the workarea's sharing group.

SOLUTION:
Specify Set Group ID (SGID) for the following parms (in iw.cfg) to ensure that all assets created in the workarea (via the UI) share the workarea's group and not the primary group of the person performing the action.

workarea_default_perm=2770
directory_default_perm=2770

sridharg

I agree with what you are saying. We mainly have problems with many of the existing files which have been migrated from old content store. Even after setting proper access permissions in submit.cfg, we notice many of the files for which the permission is not getting applied. Because of this we run into a problem when trying to generate a html, we are getting daemon error code 5 as a result.