Security: Advice Request

[Eamonn John Casey]

Hi!

Because of information security issues in my organisation we have multiple Repositories.
It is a real problem to maintain a "central" Repository that everyone can use.

The issues are:
1. Central Repository contiains elements that everyone should use. So this is distributed out using different methods. Creating new elements and distributing that out to the Local Repositories is a manual routine that takes alot of time and formality.
2. Sharing between Local Repositories is impossible. Or atleast so difficult that it simply is not done.
3. Getting elements in from the Local Repository that should be shared out to all is also admin intensive.

Anyone out there has solved the security limitations? Using Group Locking works. But others can read even though they should not have access to that information.

Thanks for any feedback.

[qwerty]

What I did in a project was simple to have a controlled package and lock that to an admin group responsible for maintaining it. That works pretty well. It needs active maintenance to keep it up to date and resolve conflicts when making any sort of change. But you can't have the cake and eat it the same time.

q.

[Geert Bellekens]

We use a connection to an external version control system (TFS or SVN) or order to share parts of our model.

You also have the option of using the Reusable Asset Service, but I've never used that before.

Geert