Group security and branching (security not copied)

Clayton · Post by **Clayton** » Wed Jul 28, 2004 6:05 pm

Our repositories are setup with an "Active" folder and a "Release" folder, indicating current and prior releases. At time of release, we label the "Active" folder and should fix be required, branch it into the "Release" folder.

Problem is we have several folders underneath "Active" in which only certain groups have access to. We want the same folders underneath corresponding "Release" folders to have same security level. However, branching doesn't seem to carry over security rights. Any ideas other than having to manually change security through admin tools every time we branch or should this be marked as a feature request?

---------------------------
Clayton Dool
Application Developer, Axium

Post by **jeremy_sg** » Thu Jul 29, 2004 7:23 am

They should be copied ( at least they used to be). I'll investigate more to see if this is a bug.

Clayton · Post by **Clayton** » Thu Jul 29, 2004 11:09 am

Actually, let me revise what I said/question... When placing security on the trunk, the branches already existing do not get the security. I assumed that new branches would be same, not having security as well. My general assumption was branches, if no security was directly set against them, would look to the parent trunk for security rights. At this point, I assume this is incorrect or a bug?

Post by **jeremy_sg** » Thu Jul 29, 2004 11:52 am

Your assumption is incorrect. Security assignments are copied at the time of the branch. New security assignments only affect the the folder where they were applied.