Book a Demo

Author Topic: Security configuration per root node  (Read 2970 times)

bernardm

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Security configuration per root node
« on: May 12, 2011, 07:06:24 pm »
Hi All,

We plan to deploy EA accross all departments of our company. Each department will have his own RDBMS repository.

Each repository will consist of multiple projects (multiple "root nodes"), some of them sharing the same artifacts. For example, the department domain model will be modelized in a separate shared root node that all projects (other root nodes) could refer to.

Moreover, each root node will typically be managed by differents users.

In such a scenario, we would like to configure EA security at root node level. How can we do that?

Thanks for your help!

Bernard

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Security configuration per root node
« Reply #1 on: May 12, 2011, 08:46:13 pm »
Bernard,

There's nothing you can do in EA itself. Security is for the whole of the repository.
What you could do is integrate EA with your version control system. In your VCS you can then grant checkout-rights only to specific users.

Geert

bernardm

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Re: Security configuration per root node
« Reply #2 on: May 12, 2011, 09:49:32 pm »
Thanks for this quick answer, Geert. Currently, version control is indeed the way to go.

I just hope to see such a feature (security configuration per root node) in one of the next EA version...

Kr,
Bernard

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Security configuration per root node
« Reply #3 on: May 12, 2011, 09:51:59 pm »
In that case you'll have to submit a feature request to Sparx.

Geert