Perfect!

Absolutely.  There is a dialog form that you can display to the end-user to manage all of the roles, users, and permissions associated with the roles and users.  It is very flexible and gives you complete control without actually having to write the end-user interface yourself.

In the same approach we have taken throughout the framework, we have implemented features that give you as much or as little control over the security that you would need. 

Hmm..how about the ability to allow users to change roles, permissions, etc.?

The security keys will be right on StandardForm... no templating required.  Just set the permission key on the form to define the permission that is required to view/edit the form and then define the permission within the database (same functionality on the field-level, too).

oooh...=)

Will we have the standard strata type forms, etc. to implement the management or will we have to build something? Yeah, I know, it's lazy, but it's Sunday...=)

Looking forward to this.

You'll be happy to know that the security will be in the next release.  Probably when 1.4.1 switches from pre-release to full release.

Yes, we support the ability to assign multiple roles to users.  However, you don't assign roles to objects, but rather a "permission key."  When you assign a permission to a role or to a user, you assign an action along with that permission.  So, when the user logs into the system, the system builds a list of the permissions that have been assigned to that user and the action(s) for each permission.  The permissions are then linked to the permission keys that are assigned to objects within the application.

As for windows security, we will definitely keep all permissions within the application's db and out of Active Directory.  We're also probably going to allow the ability to link a particular user to the SID of an AD user to allow for Windows authentication.

In the security scheme that you are designing it would be nice if you included an option to use Windows authentication (the Windows/Active Directory user ID and password) or custom authentication where the user ID and password is stored in the application DB. The actual roles would be defined in the framework and not Active Directory.

 

Also do you plan to support multiple roles assigned to both users and objects?

 

-Larry

Larry,

The overall design is relativly encapsulated.  However, if you have a desire to use Windows Security and AD, you could easily write a program to import settings and assign permissions.

Ben,

In designing your new security are you considering provding the ability to use Windows authentication and Active Directory groups (roles)?

-Larry