we have a turbine application and we're reenginneering our security model. we currently have a scattered, inflexible security model that allows users certain access to screens by tying the turbine_user table to group/screen/permision table ( a group gets permission to a screen, a user is in a group so the screen checks permission to see the user's groups permission for a particular screen.
do any turbine users out there have more enhanced security while keeping with the KISS principle? thanks! ~mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
