Branch security problem

We have done migration from Teamsite server 6.1 SP1 Solaris 8 to Teamsite 6.7.1 Solaris 10.
We have manually set the branches permission to 771 using chmod as the branch permissions were not properly set by iwaccessmigrate. After migration in new server we found all the branches are visible to all our users .We have setttings branch_security=true workarea_security=true in iw.cfg and still the branches are visible.

Find more posts tagged with

Comments

Tbag

I don't have ready access to a Solaris TS installation right now, but what happens if you do a 770 instead of 771 on one of the branches?

kaalraa

We have done migration from Teamsite server 6.1 SP1 Solaris 8 to Teamsite 6.7.1 Solaris 10.
We have manually set the branches permission to 771 using chmod as the branch permissions were not properly set by iwaccessmigrate. After migration in new server we found all the branches are visible to all our users .We have setttings branch_security=true workarea_security=true in iw.cfg and still the branches are visible.

Could you please brief out your steps of migration? Also you have installed TS 6.7.1 on a new box or its just an upgrade?

baskar

We have installed Teamsite 6.7.1 newly in the Solaris 10 server. Actually we have migrated 3 stores from the old server (Teamsite 6.1 SP1 - Solaris 8) and created a new store in new server using iwmigrate CLT. We run accessmigrate like iwaccessmigrate -o -bg -n -m and edited the accessresults.xml file to set the branch permissions from rwxrwxrwx to rwxrwx--x .Then we have rerun the iwaccessmigrate 2nd phase like
/iwaccessmigrate -o -f /CMT/iw-logs/accessresults.xml.

But that was not setting the permissions on branches. We got the information from Support that iwaccessmigrate will not set branch permissions even if we set it in accessresults.xml file.so we developed script to manually set the branch permissions to 771.We have rerun the iwaccessmigrate again in the following order

1. /iwaccessmigrate -o -c
2. touch /opt/local/CMT/iw-store/TSMigrateAccess
3. /etc/init.d/iw.server stop/start
4./iwaccessmigrate -o -bg -n -m
Now we got the branch permissions correctly set in the new accessresults.xml.so we haven't made any changes to teh xml file and have run the iwaccessmigrate second phase like /iwaccessmigrate -o -f /CMT/iw-logs/accessresults.xml

Now the problem is all the branches are visible to users who havenot got access for them.

masterdetail.zip

Frederik

Read this thread about iwEveryone that seems to get editor role on the //tsserver level. Either remove that permission entry, or set each store not to inherit role settings from parent.

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

nested_tables(2).rptdesign

nested_table_grand_total.xlsx

bcvbbbjnn

Hi

Kindly crosscheck few branches where you need to check its properties.
If the option Users and Roles is having "Inherit from Parent" option checked then the parent branch users can access the same.

Make use of the CLT iwaccess set-inheritance

Also if iwEveryOne group by default is having reviewer role for all branches then thats the issue.

Above mentioned are some possibilities of this user mgt issue.

Warm Regards
Nirmal Krishna Iyer