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; } } }

workarea_default_perm=2775

System

When I set workarea_default_perm=2775, it acts like "277".

Meaning the workarea permissions default to the following:
Owner: “Write Only”
Group: “Read/Write”
Other: “ Read/Write”

The reason we have 2775 is for group inheritance.

Is there a way to have group inheritance without the Owner permission defaulting to “write only”
Here are the steps to recreate the Bug.
1. In iw.cfg set workarea_default_perm=2775
2. In teamsite, Create a new workarea
3. Notice that the permission default to “Write Only” for the owner.

Find more posts tagged with

Comments

nipper

Did you read something that implied this works as a chmod does ? From reading the manual, it uses examples of 664, 775, etc. No place have I seen the sticky bit referenced.

This would also be a security issue if it did (not for the group sticky bit but imagine if the root sticky bit was set by TS).

You may have to create the workarea and then set the group stick bit. I cannot imagine you make workareas all too often

Migrateduser

The original problem was as follows:

1. When we set the "group" of a parent folder, the child folders and files does not inherit the "group".

2. So interwoven told us to add the sticky bit to enable inheritence.

3. Adding the sticky bit causes the workarea and "all files/folder " created in the workarea to default to "write only"

See the interwoven article below for details about the sticky bit:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=60722

nipper

Well OK then. I did not realize that was supported. Sounds like a bug. Report the bug to IWOV, use 775 and apply the sticky bit when you make a new workarea until a patch/workaround/resolution is provided.

cpm_dst

How are you determining what permissions have been set?

If you are using the Content Center interface you will see the permissions as:

owner: Write only
group: Read and Write
others: Read and Write

If you check the folder permissions via /iwmnt you should see they are correctly set as:

drwxrwsr-x

This appears to be an issue with the CC interface display of the permissions, not with the actual TS functionality.

Hope this may help.