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

User / group concept in Teamsite 6.7

vikaslohia

Hi,

I am using teamsite 6.5.2 and planning to upgrade to 6.7.2. Going through the different documents, I understand that the user access / role concept has been changed in 6.7. I have a question on this -
My teamsite installation makes use of customized code for user creation in teamsite 6.5.2. I need the new users (along with role) to be added to my customized database (along with author.uid file). Hence, to create a new user, I have a GUI which makes entry to my customized database and then adds the userid in the author.uid file.

My understanding about 6.7 is that this version has combined all the uid files (author.uid, master.uid, etc) into a single file called tsusers.xml. Hence, I think if I change my customization part to write the new user details to tsusers.xml in the required xml format along with the custom database entry, then the application would continue working in the same way as it is currently.

However, I would then be bypassing the teamsite way of creating new users in 6.7 and effectively updating the tsusers.xml file to create new users.

Based on above, is my understanding correct? Would updating the tsusers.xml file directly cause any issue?

Regards,
Vikash

Find more posts tagged with

Comments

Adam Stoller

Hi,

I am using teamsite 6.5.2 and planning to upgrade to 6.7.2. Going through the different documents, I understand that the user access / role concept has been changed in 6.7. I have a question on this -
My teamsite installation makes use of customized code for user creation in teamsite 6.5.2. I need the new users (along with role) to be added to my customized database (along with author.uid file). Hence, to create a new user, I have a GUI which makes entry to my customized database and then adds the userid in the author.uid file.

My understanding about 6.7 is that this version has combined all the uid files (author.uid, master.uid, etc) into a single file called tsusers.xml. Hence, I think if I change my customization part to write the new user details to tsusers.xml in the required xml format along with the custom database entry, then the application would continue working in the same way as it is currently.

However, I would then be bypassing the teamsite way of creating new users in 6.7 and effectively updating the tsusers.xml file to create new users.

Based on above, is my understanding correct? Would updating the tsusers.xml file directly cause any issue?

Regards,
Vikash

You would be better served to read up on the new CLTs that go along with the change in user / role management.

Yes, you can modify tsusers.xml manually / programmatically - as long as you don't mess it up, it won't cause any problems.

However, tsusers.xml (as the name implies) is just a list of users - not roles (except for Master) - whereas before 6.7 roles were assigned globally across all branches on the server, since 6.7 roles are assigned on a branch-by-branch basis and managed within those branches (not in a central configuration file).

You should look at CLTs like iwuser, iwaccess, etc.

Hopefully you have a DEV system to work on to figure all this out before you try to upgrade your production system.

Migrateduser

Some general comments on user admin between versions:

We're currently on 6.7.1 on Solaris. We upgraded to 6.7.1 from 6.1.

Back on 6.1, we managed our groups by adding them first to the OS and then into a mass of OS-level groups that controlled various access and workflow capabilities.

In 6.7.1, we still add all of our users to the OS, but have them all in a single OS group and then we use TeamSite groups to control all of the access and workflow capability work we used to do with the OS groups. TeamSite groups are incredibly handy and more flexible than the OS grouping we used previously. Our workflows take lots of advantage of these TeamSite groups.

We don't have any sort of LDAP / AD integration at this time.

It did take a good bit of analysis and scripting to perform the migration between 6.1 and 6.7.1 of the users and groups - but it was well worth it. And I really can't imagine getting that done on an in-place upgrade, although I suppose it's possible. We upgraded by moving to new hardware.

I believe that 6.7.2 has now eliminated the need to establish the users at the OS level? Does anyone know if this is true? I'm doing some analysis on 6.7.2 before planning an upgrade and ran into this posting.

Wally Box
Nike, Inc.

nipper

I believe that 6.7.2 has now eliminated the need to establish the users at the OS level? Does anyone know if this is true? I'm doing some analysis on 6.7.2 before planning an upgrade and ran into this posting.
.

Yes that is true with some constraints. If I have a non-os user (as defined in ts-users.xml) then Unix cannot run a process under that person's name. That means you cannot use TPL based templates and you cannot execute an external task with the username as the owner.

ISCBorisB

I believe that 6.7.2 has now eliminated the need to establish the users at the OS level?

Take a good look at [thread=27388]this[/thread] thread