Permission issue with iwgen CLT

anjani

Hi,

I am using iwgen CLT to generate the XMLfiles from the DCRs. But i am facing one issue, so need your suggestions to resolve that.

Problem Statement:
-------------------

We have one xml folder parallel to data folder. The data folder has rwx permission for owner (Say A) and group (say Group_B) but for others it has rx permission.

In script we are calling the "iwgen" CLT to create the xml files under XML folder. XML files are created fine if the script is run by user "A" or users who are part of group 'Group_B'.

But the permission denied error comes when who has admin role on the branch under which XML folder is there but admin is not part of the group 'Group_B'.


So the problem is if the user has admin access on the branch under which XML folder is there and can create new file under XML folder using teamsite "New File" link, then why iwgen CLT is throwing permission denied error.

Any pointer/suggestions will be appreciated.

Thanks,
A.S

Adam Stoller

Hi, I am using iwgen CLT to generate the XMLfiles from the DCRs. But i am facing one issue, so need your suggestions to resolve that. Problem Statement: ------------------- We have one xml folder parallel to data folder. The data folder has rwx permission for owner (Say A) and group (say Group_B) but for others it has rx permission. In script we are calling the "iwgen" CLT to create the xml files under XML folder. XML files are created fine if the script is run by user "A" or users who are part of group 'Group_B'. But the permission denied error comes when who has admin role on the branch under which XML folder is there but admin is not part of the group 'Group_B'. So the problem is if the user has admin access on the branch under which XML folder is there and can create new file under XML folder using teamsite "New File" link, then why iwgen CLT is throwing permission denied error. Any pointer/suggestions will be appreciated. Thanks, A.S

Branch and workarea access and functions are handed at the TS role level.
Directory and file access are handled at the OS access-rights level.

So just because your user has TS Administrator role on a given branch does not mean that user has actual read/write/execute permissions on the files and directories within that branch.

Quick-fix - add the admin user to group B.