Protecting Sparx Jscript code

[BruceTOGAF2]

Using the Sparx Security Model, I can prevent other users from editing Sparx script code.  If a user is not permitted to edit scripts, then (within the Scripting window) the 'Edit' option is greyed out in the Script context menu. 

If a user is permitted to run scripts but not edit scripts, then the 'Edit' option is greyed out but the 'Debug' option is not greyed out. By selecting 'Debug', the code is displayed. The user cannot edit the code but they can copy and paste the code.

How can I disable the 'Debug Script' option whilst enabling the 'Run Script' option?

[Geert Bellekens]

I don't get it, why would it be a problem if a user sees the code?
If they want they can query the database for it as well, there's not really anything you can do about that.

Honestly I would forget about it. If a malicious user wants to do harm, they will not be stopped by EA's security features.
There are just there to prevent oopsies.

Geert

[qwerty]

While Geert is absolutely right you can always send a bug report/feature request (along with your wish list for Santa).

q.

[Uffe]

Hey guys,


I would agree that with the current set of scripting permissions available, Edit vs Run, debugging a script should fall under Edit rather than Run -- debugging is part of development. It shouldn't be a particularly hard fix for Sparx either, it's a pretty simple function that doesn't affect a bunch of other stuff.

So I think it's worth it to send a bug report.


/Uffe