Security on Package control

[John Brand]

Under security a user or group of users ca/cannot perform certain functions. Within a project it is quite often the case to have several teams working onm different parts of the project. It should be possible to restrict authority by package.

[Geert Bellekens]

That would indeed be a nice feature.
The "standard" workarounds for this are:
- Group locks
- External version control (where you define the rights to checkout/in)

Geert

[John Brand]

Thanks Geert, we decided on Auditing plus rigorous security rather than version control but group locks sounds interesting; can they be applied to distinct packages?

[Geert Bellekens]

IIRC you can use group locks to enable write access only for a specific group.

But I've never used it myself.

Geert

[qwerty]

Yes, you can do that. Group/user handling in EA however is a bit clumsy.

q.

[John Brand]

Could you be a little more specific on that please?

[qwerty]

You can create and name an arbitrary number of groups which you can use to lock packages (and all their contents). Further you can assign each user to any of these groups. Once you have enabled security via the key you got from Sparx you need to log in as admin/password and then create the appropriate groups. You can import the users from Windows if you check Accept Windows Authentication. Or you create the users locally to EA. Once done you can assign the groups to the users.

q.

[John Brand]

Thanks

[andykennelly]

Qwerty - I've created some groups and added users to them. How do I then apply package locking at the group level? I can only see how to lock at the user level (even though that user is in a group). Is it one of the package control options?

[Geert Bellekens]

From TFM

To check whether the project security is in User/Group locking mode, select Project | Security; the [highlight]Require User Lock to Edit option should be deselected[/highlight]

Geert

[andykennelly]

Excellent!! I've got it sorted. Many thanks for all the help.