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

Issue with setting the group owner of DCRs

dolly1

Hi,

I am having an issue with propagating the same group owner permission to my DCRs as the workarea / templatedata / content type folder has.

My WA, templatedata and content type folder has owner as iwadmin and group owner as group1. The permission are iwadmin and group1 has read and write permission and others have read permission.

I have gone through the following posts:

http://devnet.interwoven.com/forums_vb/showthread.php?t=24305&forumid=11&highlight=sgid

http://devnet.interwoven.com/forums_vb/showthread.php?t=27109&forumid=11&highlight=owner+group+teamsite

http://devnet.interwoven.com/forums_vb/showthread.php?t=25378&forumid=11&highlight=owner+group+teamsite

and did as per what these posts say.

First is setting workarea_default_perm=2770
directory_default_perm=2770

does not seem to be working. Because i did these changes, restarted teamsite and then created a new workarea with all proper permissions and owners as mentioned above still while creating a DCR the group was coming as others only which is the primary group of the user.

When i do what ghoti has mentioned in one of the posts like

% find dtype1 | xargs -n 1 iwchgrp tsg1
% find dtype2 | xargs -n 1 iwchgrp tsg2
% find dtype1 dtype2 -type d | xargs chmod g+s

then my WA, content type and data folder permission gets changed from

owner(iwadmin) was earlier read and write now it becomes write only.
group owner (group1) remains the same read and write.
others get changed from read only to read and write.

but now the group is getting properly set on the DCRs and the permissions on the DCRs are fine

owner(xuser): read and write
group owner(group1): read and write
others; read only

Please help me to understand why WA, content type and data folder permission is getting changed.

Find more posts tagged with

Comments

RonaldV

TS version & patch level?
OS version & patch level?

But let's give you a some hints:

1. you don't mention file_default_perm which is probably what you want. See page 64 of the admin guide for more info

2. What you describe is exactly how Solaris works: if a user creates a new file Solaris adds the user's primary group as group for the file. And it uses the chmod-permissions from the users-profile, I believe.

3. If you want to change this, in a way supported by Teamsite, see the section on submit.cfg in the admin-guide.

Good luck, Ronald

dolly1

Thanks for the reply.

TS 6.7.1 SP1
OS: solaris 10

I did try with file_default_perm as well but it did not make any difference.
I do not have any submit.cfg file present in my teamsite but i guess its pretty much the same if i set the branch and WA permissions manually or using submit.cfg.

Also I am facing the issue as soon as i create the new DCR, i guess submit.cfg gets applied when you submit the DCR to staging area.

Any thoughts?

RonaldV

Yes, submit.cfg actions fire on submit.

Adam Stoller

...
When i do what ghoti has mentioned in one of the posts like

% find dtype1 | xargs -n 1 iwchgrp tsg1
% find dtype2 | xargs -n 1 iwchgrp tsg2
% find dtype1 dtype2 -type d | xargs chmod g+s

then my WA, content type and data folder permission gets changed from

owner(iwadmin) was earlier read and write now it becomes write only.
group owner (group1) remains the same read and write.
others get changed from read only to read and write.

but now the group is getting properly set on the DCRs and the permissions on the DCRs are fine

owner(xuser): read and write
group owner(group1): read and write
others; read only

Please help me to understand why WA, content type and data folder permission is getting changed.

If not - it's difficult to verify where the permission problem came into effect - and you'll simply have to fix the mode bits manually (verify them) and then submit them again (and re-verify).Also - make sure you are verifying the permission in the workarea and not in STAGING or an EDITION.If the permissions look correct before submitting but wrong after submitting - the culprit is probably your IWHOME/local/config/submit.cfg file, though it is possible the settings in your iw.cfg might cause problems and/or the umask of the user who owns the TS server process.

testrst1form1.rptdesign

tanguyr

does not seem to be working. Because i did these changes, restarted teamsite and then created a new workarea with all proper permissions and owners as mentioned above still while creating a DCR the group was coming as others only which is the primary group of the user.

Did you create a new empty workarea or did you create a workarea based on an edition with files/folders in it? If the second, then the folders in the workarea will have the permissions of the folders in the edition, i.e. they won't have the sgid set. Easy check is to use clt "iwaccess unix-permission [vpath]" to display - check that you see the "s" in group section (so like "rwxrws---". You can also use option "set-unix-permission"

When i do what ghoti has mentioned in one of the posts like

% find dtype1 | xargs -n 1 iwchgrp tsg1
% find dtype2 | xargs -n 1 iwchgrp tsg2
% find dtype1 dtype2 -type d | xargs chmod g+s

then my WA, content type and data folder permission gets changed from

owner(iwadmin) was earlier read and write now it becomes write only.
group owner (group1) remains the same read and write.
others get changed from read only to read and write.

but now the group is getting properly set on the DCRs and the permissions on the DCRs are fine

This second bit (strange looking perms in Content Center) is just a bug - CCPro (and CCStd?) can't correctly display the perms on a folder with the sgid set - see here: http://devnet.interwoven.com/forums_vb/showthread.php?t=27712&forumid=11