|
Adam, Sometime ago I set up a crude ODBC authorization tool in our shop using, besides the exit point, a control file that specified the User ID and the "access level" that user had (SELECT/INSERT/UPDATE/DELETE). So what I did was to scan the SQL statement and, if it had a keyword I didn't like according to the access level (SELECT/INSERT/UPDATE/DELETE) the statement was denied (Did I mention it was crude approach?). There was also a list of statements that weren't allowed under any circumstances (eg., ALTER, GRANT, REVOKE, etc). HTH, Luis Rodríguez Luis Rodriguez IBM Certified Systems Expert — eServer i5 iSeries
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.