Author Topic: Restricted package visibility with WebEA  (Read 7192 times)

blaisephilip

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Restricted package visibility with WebEA
« on: July 13, 2022, 11:20:20 pm »
Currently our organization is working with the following setup:
Sparx EA V16.0.1604
Sparx Pro Cloud Server v5.0 (Build 104)
Sparx Prolaborate 4.1.2.0[/li][/list]

Package visibility is used successfully to restrict user access to some project packages via sections in Prolaborate and via AD Group-based visibility configuration in EA.

However, in WebEA even a user with restricted access towards selected packages can see everything in the model repository. We would not like to turn WebEA off since it helps some scenarios, but it would also be in our interest to hide the packages in question in all 3 systems. (EA-based model editing scenarios, WebEA, Prolaborate)

Is this possible?

wivel

  • EA User
  • **
  • Posts: 236
  • Karma: +12/-1
  • Driven by Models
    • View Profile

blaisephilip

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Re: Restricted package visibility with WebEA
« Reply #2 on: July 14, 2022, 06:26:17 pm »
Thank you, I hoped that we can keep using MySQL, but the row-level security is not supported there, so it would cause a DB transfer for each repository.
I think the only proper way to handle our use case (without additional DB-support-setup on the server) is to migrate the packages with higher confidentiality to another repository without WebEA-activation, but with connection to Prolaborate.

wivel

  • EA User
  • **
  • Posts: 236
  • Karma: +12/-1
  • Driven by Models
    • View Profile
Re: Restricted package visibility with WebEA
« Reply #3 on: July 14, 2022, 11:35:42 pm »
Makes sense. A more practical approach that will wok no matter the DB Technology, security model and what not.

Henrik