Solution import missing security?

Classic Servoy
1

Hello!

When importing a solution to the repository, I noticed that user group security settings didn’t get imported. The groups were loaded but not the individual form and table access rules. Is this a bug?

Servoy 2.2rc4

2

Ok, found out that I have to have a user in every group in order to get the group security data loaded. But it still doesn’t store the “tracking” bit of tables? This is not a big issue but still a bit annoying.

3

It looks a bit strange indeed.

The idea is that security (table security, tracking bit, etc) is always transferred in the export regardless of whether you have users or not. Similarly with group security settings.

Users themselves are NOT exported (unless you check the box which says that you DO want users in the export).

If you have an example solution which exhibits this behavior it would help me look into the problem.

4

sebster:
It looks a bit strange indeed.

The idea is that security (table security, tracking bit, etc) is always transferred in the export regardless of whether you have users or not. Similarly with group security settings.

I can confirm, the security groups settings are not imported until a user is present in every group. My solution is quite complex but i can send you a copy for testing purposes.

5

That would be nice, saves me the time of having to try build solutions which reproduces the problem.

6

sebster:
That would be nice, saves me the time of having to try build solutions which reproduces the problem.

Just sent my solution to your email address.

7

Any news on this issue?

8

This has become a bit annoying- every time we import a new solution release to the server, all the table tracking bits get cleared. So we have to click through every security group, and every table that needs tracking, checkbox and update button.. It shouldn’t work this way.

9

When you import a solution and import the group/table security settings, all local settings will be clobbered. So any changes you made locally which are not in the import, these will be overridden.
However, the security settings should after import accurately reflect what is contained in the import. I am quite sure I found out what the issue is, and a temporary workaround should be a restart directly after the import. Of course I will resolve this bug for the next release.

10

sebster:
When you import a solution and import the group/table security settings, all local settings will be clobbered. So any changes you made locally which are not in the import, these will be overridden.
However, the security settings should after import accurately reflect what is contained in the import. I am quite sure I found out what the issue is, and a temporary workaround should be a restart directly after the import. Of course I will resolve this bug for the next release.

Ok; thanks for the reply! Somehow I have learned to restart the application server to fix some problems, but didn’t notice it was connected to the security settings also.

11

Hi,

Unfortunately the bug I was looking at was not the one that caused this issue. I fixed it now and it will be available in the next build. A server restart will not solve the problem in this case.

12

Hello, I have a problem where users are simply not imported at all. I have set the “Overwrite existing users completely” and “Allow users to be added to the Administrators group” checks but I only see the the groups imported. The table servoy_users in the repository is empty and I see an info after the import saying “Skipped user information” several times.

The repository was completely empty before the import of the solution.

Latest Servoy build.

13

Did you export the users? Are they contained in the .servoy file? That way I can check on which end the problem is: import or export.

14

It’s import :-). The users are included.

But! I see for example this entry:

Ruhsert, Patrick G. bQDfUG7teBdZM7Xs3ih8ZA== Tracking

I am also member of the Administrators group and there is no hint about that. All exported users I see are only member of this group, but no other (and there is two more, see below).

And one more:

We have 3 groups:

  1. Administrators
  2. Tracking
  3. A third group

The tracking group is created in the new repository. The third group is not.

And last:

I noticed another problem when importing the solution. Obviously Servoy tries to create the log table twice and fails. At least when I first try to import into a blank repository all tables are properly created but the import fails with an error saying that the log table already exists. When I reimport, everything is fine. In my case the log table is in the same database as the “rest”.

Thanks
Patrick

15

We have had exactly the same problem. We are working with several modules in a solution and when we import the latest version of the Clients module, no users are moved over from the Client module. The original users in the importing module remain unchanged.

16

Wnen you export a solution with users, only users are exported that are in groups which are in use by the solution, and only the user’s groups are taken that are used by the solution.

So if a solution does not make reference in the security settings to the “admin” group, then when a user is exported, the user is not included in the admin group (since Servoy concludes that the admin group has nothing to do with the solution.

So the above explains why the .servoy file looks as it does. Now for the import part of the explanation… :)

Well, it turns out there is a really stupid bug in the html of the admin server page for the import, in which the options are a bit confused.. When you say:

  1. do not import the users, it actually does what it says in the next bullet, which is ‘create non-existing user and add to groups’…
  2. create non-existing users etc, it actually does what it says in the next bullet, which is ‘overwrite existing users completely’
    and finally, when you say
  3. overwrite, it actually does nothing…

So, as you can see, selecting option 1) (do not import users) is probably the way to go. :-)
The bug will be fixed in the next release…

17

sebster:
So if a solution does not make reference in the security settings to the “admin” group, then when a user is exported, the user is not included in the admin group (since Servoy concludes that the admin group has nothing to do with the solution.

Sebastiaan,

I think I don’t get this. What do you mean by “reference”? How does a solution “reference” a group? If I put a user in the admin group on repository A and move that solution to repository B, I’d expect that user to be in the admin group of B as well.

Do you mean by “reference” that a solution relevant security setting is used in that group (for example tracking) for that solution? If yes, I could just make every group track some irrelevant table to overcome this, right?

But somehow I don’t exactly get the concept behind it…

Thanks
Patrick

18

Yes, that is what I mean.

A solution has group security settings. If for a specific group NO security settings are set in the solution, the group is simply not exported. If a group is not exported, then it is also not contained in the user info in the export.

Your workaround works. You can set some kind of security for the admin group on some kind of irrelevant table if you want, and the group will be exported and also be contained in the user info.

19

It works as you said. Thanks.