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

Teamsite groups - editing tsgroups.xml

andy_b

Hi,

I am considering using the tsgroups.xml file for group administration to reduce our reliance on our ITS dept continually doing user and group maintenance on our TeamSite server (Solaris).

Also, as we don't have root access to our server (only our IT dept does), and you need to run iwgroup as root, I was wondering what the implications would be of changing the permissions on the tsgroups.xml file so it could be edited either manually or via another method (php web interface?) by a TeamSite administrator. For example, would an accidentally ill-formed tsgroups.xml file cause TS to become unstable or crash? Would changing the rw permissions or group ownership of the tsgroups.xml file cause problems?

Anyone had any experience with these issues?

Andy

Find more posts tagged with

Comments

Johnny

This doesn't really answer your question, but if you're thinking about creating an interface for a xml file, consider using the templating interface.

John Cuiuli

Adam Stoller

The permissions of tsgroups.xml probably has little, if anything, to do with your issue here. iwgroup currently needs to be run as root (sudo should work as well) - and so unless you have root or sudo permissions you won't be able to do *anything* with the iwgroup CLT.

This includes querying the group information (Feature Request # 57864 has been filed to allow non-root users to query information using iwgroup).

As root, you can feed iwgroup any properly XML-formatted file you want, with any permissions (that you can read) on it to make changes to the group entries in the system.

If the data isn't formatted correctly, my guess is that iwgroup will abort operations before anything happens (at least I'd hope so) rather than making potentially harmful modifications to the actual group entries in the system (anyone care to confirm this?)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

andy_b

We can get the permissions changed on the tsgroups.xml file as a one off request to our IT dept so that we can edit it.

That's why I was wondering if it's file permissions/group ownership would affect any other TS operations, especially when TS reads tsgroups.xml to determine group sharing of branches/workares, and also because we are looking for alternatives to using the iwgroup CLT (we don't have root access on our production server to run it).

Johnny suggested using forms publisher, which in conjunction with OpenDeploy could be the answer we are looking for.

As long as we can either
a) change the permissions on tsgroups.xml or
b) OpenDeploy can deploy tsgroups.xml from a workarea in TS to /bin/conf/ and allow it to have it's correct/original group ownership and file permissions once deployed.

Johnny

I wonder why this isn't available in the Administration tab?
You may as well start a feature request now.

John Cuiuli

Adam Stoller

Along with having OD deploy the modified tsgroups.xml file to the system you'll probably want a DNR script to run as root to execute iwgroup and read-in that file (in fact, as I indicated before, you can use any properly formatted file as the input to iwgroup - it doesn't have to be tsgroups.xml)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com