Security group management

Questions
1

Hi

security.createGroup(aName) and security.deleteGroup(aName) are marked deprecated in newer Servoy developers.
Are there any alternatives available?

Kind regards
Birgit Rieder

2

Hi Birgit,

Security Groups have been renamed to “permissions”, the creating (or deleting) of which is now reserved for a design-time, developer activity.

Best,
Sean

3

Hi Sean

Thank you for the answer.

So, there are no plans for an alternative for the deprecated methods? We then have to remove the function from our customers to manage groups (permissions) by themselves :(

Kind regards
Birgit

4

Hi Birgit,

To me, using Servoy Groups is only valuable if you are really using the build in permission structure. (ie ‘security’ tab on a form)

If you are using the groups just as a ‘permission label’, easy solution would be to create your own table with groups and link your users to these groups.
Concerning Servoy groups, you basically need only 2 (predefined) groups: ‘Administrators’ and ‘Users’

5

Hi Marc

Thank you for the response.
I’ll have to rethink about how we really handle access rights and the group management.
We actually have our own group table. But we also create security groups.
Maybe that’s too much?

Thank you again, you have given me something to think about ;-).
Regards
Birgit

6

Hi Birgit, why do you need to crate groups/permissions at runtime via API? Or more specifically, why do end-users need to create permissions? And what would they do with a permission that they created? What are the “hooks” to he application? (i.e. can see a field/button or can delete on a specific table, etc)

…Because as Marc points out, these permissions really have significance in the element and table security which is a design-time thing. (That is why it is deprecated from the API)

7

Hi Sean

Thank you too, for the response. As I mentioned, I have to rethink about our security settings and management. I’m glad, if I can come back with questions, as soon I have figured it all out.

Best regards
Birgit

8

Ah, I see now, we did implement this too complicated. Our own groups are enough. For security.login, we only can use ‘Users’. No keeping in sync. Thank you for the answers.
Kind regards
Birgit