...
There isn't a standard way of doing programmatical security of this nature - the nature of it is such that you have to write it yourself.
That is essentially what I'm trying to do, using various built-in tools , such as java.security.acl.*, sun.security.acl.AclImpl, sun.security.acl.AclEntryImpl, sun.security.acl.PermissionImpl, etc. I'm just having trouble figuring out how these tools are intended to be used
Programmatical checks at each read/write point, using username based SQL queries if your user can be linked/related to the stock DB, it's a logical problem more than Tomcat problem I think.
I know it's not primarily a Tomcat problem, which is why I initially posted in comp.lang.java.security. However, there are still no responses there after two days.
Thanks for the comments! Dave --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
