Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: philchudley on September 18, 2018, 08:06:24 pm
-
I have received a request from a client to restrict who can disable / enable Add-ins / Extensions.
Having checked the List of Available Permissions, there does not appear to be any such permission, and a test of:
- creating a new user with no permissions at all
- logging in as that user
- selected to Manage Add-ins, was able to enable / disable any listed Add-in
As workflow scripts only apply to selected element properties, that route won't work either.
Is there a way to prevent users from Managing Add-Ins?
Thanks
Phil
-
Yes. Extend the add-in to check for the user.
q.
-
Yes. Extend the add-in to check for the user.
q.
How would that work if the add-in is already disabled?
I don't think there is an event for enabling/disabling add-ins.
And I think Phil also wants to be able to restrict enabling/disabling any add-in, not only his add-in.
I guess you'll need to send in a change request.
Geert
-
You are correct Geert
Basically, the client has diabled audit due to performance issues, so the Add-in "mimics" the audit by monitoring for events "behind the scenes" and writes info to its own log files.
Since this addin must run for all users, any user should not be able to disable it, thereby by-passing the add-ins audit factility.
It is possible to restrict privilige to manage audit, so I was looking for a similar function.
One possiblity is to remove the Manage Add-ins from the Ribbon, but this would mean a change to each EA client.
Will send a feature request to add such a privilege.
Thanks
Phil
-
Are you sure all of this is really worth it?
If someone has bad intentions you are not going to stop him with something like this (it certainly wouldn't stop me ;D).
And in my experience, people acting in good faith are not likely to be wandering into an area such as the Manage Add-ins to disable an add-in.
Geert
-
[SNIP] (it certainly wouldn't stop me ;D).
[SNIP]
Geert
Yes, but you're Belgian - and not to be trusted! ;) ;D
Paolo
PS: Almost as bad as the French!
PPS: This is an attempt at Aussie inter-mate humour (see the icon). It may fail...
-
Can't be done with security permissions because they are model based. When in another model (or no model) they would have no effect.
In EA there's not much to you can do. The main option that I can think of is to lock down their computer so they can't install an add-in in the first place.