nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Need script to set TeamSite Group Attribute in 6.7

System

With new ability to delegate access within a branch, only newly created files inherit permission from folder. Need a script to set TeamSite Group for existing files (approx. 2000). Not been successful in reading group attribute. Can only get list of attributes.

`/cust/iw-home/bin/iwattrib -l $fileName`

Understand how to read/set extended attribute. How do I read/set group attribute?

Find more posts tagged with

Comments

moonkhanna

Understand how to read/set extended attribute.
use iwextattr clt
How do I read/set group attribute?
use iwgroup clt

Migrateduser

How does that translate to code within an iw_perl tag please? I do not have administrator access, thus don't have the ability to use CLT.

Thanks for your quick reply!

I was able to read the attribute using

$groupAttribute = `$iwhome/bin/iwattrib $fileName "group"`;

now I need to be able to set this attribute (similar to setting an extended attribute using $iwhome/bin/iwextattr -s

moonkhanna

unable to understand your question. please explain your requirement in detail.

Migrateduser

I just did this
$groupAttribute = `$iwhome/bin/iwattrib $fileName "group"`;

It returned the permission for the file.

Now I need to be able to set this attribute for this file to something different

(similar to setting an extended attribute using $iwhome/bin/iwextattr -s)

nipper

iwattrib is a read attribute command, it will not change the attributes.

Your question has already been answered, use iwgroup. If you cannot do that due to permissions issues, then talk to the admins of your server.

Now why are you asking to do this inside a TPL (iw_perl tags) ?

Migrateduser

I am a developer within the state of Oregon. The TeamSite product is owned and administered by a different state agency. I am maintaining templates, but not administering TeamSite.

We upgraded to 6.7.1 and now I am managing access via TeamSite rather than another agency managing access for me via UNIX. Currently, my agency can access all of our files. I intend to segment access for about 12 different content management teams and lock them out of folders that they are not responsible for. TeamSite will inherit folder permissions for any new file that is created. I am trying to avoid manually setting permission for 2,000 existing files. There should be a way to script this, I would think.

Thanks again for all your help!

themes.zip

Adam Stoller

I am a developer within the state of Oregon. The TeamSite product is owned and administered by a different state agency. I am maintaining templates, but not administering TeamSite.

We upgraded to 6.7.1 and now I am managing access via TeamSite rather than another agency managing access for me via UNIX. Currently, my agency can access all of our files. I intend to segment access for about 12 different content management teams and lock them out of folders that they are not responsible for. TeamSite will inherit folder permissions for any new file that is created. I am trying to avoid manually setting permission for 2,000 existing files. There should be a way to script this, I would think.

Thanks again for all your help!

If the distinction for group ownership is based on branch and/or directory boundaries - submit.cfg is the way to go to make sure the permissions are set correctly whenever something gets submitted. This requires the ability to either create or modify that config file (iwhome/local/config/ on local disk, or in an admin branch if you have one, from which it gets pushed to the local disk) afterwards you need to run iwreset -- Read the TeamSite Administrator's Guide for more details.

If you want to make sure that all files created / modified within a given directory use the group permissions that are on that directory instead of the individual user's primary group (you appear to be on Unix) - you can do a chmod g+s on the directory(ies) and make sure the group ownership on the directories are correct (note: I have not tried this [recently] with TS Groups on directories, so I'm not sure if it works correctly in that regard)

The iwgroup CLT is for creating / managing TS groups - not to set permissions on files or directories. I believe for that you need to use iwaccess.

From the GUI you can select Properties on a file or directory and might be able to alter the owner / group permissions that way - but I'm not too sure about that.

Note that setting access rights on files and directories is not the same as extended attributes (i.e. iwextattr does not apply unless you're dealing with metadata)

moonkhanna

If the distinction for group ownership is based on branch and/or directory boundaries - submit.cfg is the way to go to make sure the permissions are set correctly whenever something gets submitted. This requires the ability to either create or modify that config file (iwhome/local/config/ on local disk, or in an admin branch if you have one, from which it gets pushed to the local disk) afterwards you need to run iwreset -- Read the TeamSite Administrator's Guide for more details.

If you want to make sure that all files created / modified within a given directory use the group permissions that are on that directory instead of the individual user's primary group (you appear to be on Unix) - you can do a chmod g+s on the directory(ies) and make sure the group ownership on the directories are correct (note: I have not tried this [recently] with TS Groups on directories, so I'm not sure if it works correctly in that regard)

The iwgroup CLT is for creating / managing TS groups - not to set permissions on files or directories. I believe for that you need to use iwaccess.

From the GUI you can select Properties on a file or directory and might be able to alter the owner / group permissions that way - but I'm not too sure about that.

Note that setting access rights on files and directories is not the same as extended attributes (i.e. iwextattr does not apply unless you're dealing with metadata)

Yes, iwaccess is the right clt.. .just a bit of ambiguity by brain in processing the request.. :-)

Migrateduser

Thank you again for your help. I did succeed at resetting the group permissions of a file using iwaccess set-group vpath group.

I am also able to set the permissions with the GUI, but I wanted a better way that doing that individually for 2,000 files.