Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: GBeutler on April 18, 2008, 04:50:00 am
-
Hi All,
I would need a kind of security. I studied the docs already. What I am missing is to restrict read access to packages. Only groups or userers should be allowed to access packages of a repository. In security docs I found that I can restrict update, export etc. but not restriction of read access. There is another task about organizing huge repositories. Maybe that dividing the repository is the solution. My problem in this case would be that the same svn xmi export would be accessed by several db repositories. Has anybody experience with this kind of version control and repository separation?
Thanks in advance and
best regards,
Guido
-
We have them and it is problematic. EA has no response for read permissions per package.
We are working with some start-up company to supply some kind of "views" mechanism over EA.
You can try this mail:
levita dot gal at g mail dot com
-
If you use a private repository model you should be able to solve this using your version management system, ie Perforce or whatever restrict read access to the XML-files representing the specific package that some users should not be allowed to access...
If you use a shared repository model you will however need support for this in EA since as it is today the first time a user with read access to the "secret package" imports it to the model it will be visible to everybody :-X
-
yep, that meaning I would have to create a new configuration/EAP/DB for each type of group with different read access...real fun...