Advice call: using Servoy groups vs. rolling own security

Hi,

I’m migrating a solution from Filemaker, where we have a users table, a roles table, and a roles_assignments table. It seems like I can accomplish a lot of the same stuff with Servoy’s built in security, but I’m afraid I’m not thinking of something that will come back and bite me down the road.

Anyone seasoned Servoy developers want to share their experiences? What factors influenced your decision to rely on Servoy security or roll your own?

Thanks!

Andrew

You can do almost everything with the builtin security system of Servoy, I use it extensively in many of my apps and when it falls short you can always integrate it with your own users/groups tables. Being able to show/hide/lock each element on a form is awesome and something I can’t consider to live without.
On the other hand if you are thinking of building an ASP system you must code at least a part of your security system yourself.
IMHO the only shortcoming with security right now is that you define your security rules server-wide while a solution-wide security would be more effective (think about ASP), it would be nice to be able to present the solutions list filtered by the login name/group and to define groups and rules specific for each solution.

My advice: go for the bultin security and in the future if you need more features you can integrate your own tables with the standard security system.

A while ago Jan Aleman told me that security was scheduled to be upgraded in an upcoming release, I hoped it was in 3.0 but it seems it didn’t make it, maybe in 3.5?

My advice: go for the bultin security and in the future if you need more features you can integrate your own tables with the standard security system.

Exactly how I do it. One of the reason is that it enables me to conveniently use the ability to enable/visible the elements inside the security section without scripting…

IT2Be:

My advice: go for the bultin security and in the future if you need more features you can integrate your own tables with the standard security system.

Exactly how I do it. One of the reason is that it enables me to conveniently use the ability to enable/visible the elements inside the security section without scripting…

Enough is enough…
If the Master says so you need to look no further. :D

Nicola,

I get complaints. My girlfriends is upset now. She doesn’t want to call me ‘the master’. She also says I am not always right and that your attitude touches my attitude. She also says she is the one that has the live (or is it ‘put up’) with me. The last quote is ‘dat moest er nog bijkomen’ (Dutch). In English that is somewhat equal to ‘enough is enough’.

:) GO ON, PLEASE GO ON…

By the way she also ordered me to point you out when you come to Servoy World…

As you wish, my Master.

:D

OhOoooh

Arghh!!!
I cannot defeat TeleTubby!!
Your girlfriend has won… but if she doesn’t want to switch to the dark side maybe someone else will do it…
Enough work for today… it’s friday night and I’m a Sith so… alcohol time!!! :D

Nicola, please believe when I say not all dutch people are mentally as ill as Marcel. :wink:

back on topic… We often see developers combine the servoy security with custom build stuff.
eg. navigation buttons that are defined in a table.
These tables often have a column that stores servoy group_id
in order to control what buttons the logged in user is allowed to see.

Marcel is “THE MAN”!!!

:-)

Rich

P.S. Marcel… how do you find time to write all these plugins AND have a girl friend!!!

Hmmm, don’t ask her :)

To be honest, we both like working…