Re: Database Security

settler@hobbes.dbintellect.com (Jeff Craig) wrote: :This is certainly true if you grant update privileges specifically :to that user. However, using version 7.1 feature enhancements, you :can prevent this. First, revoke the update privileges from the user :and grant him or her only select privileges. These become their :default privileges. Next, create a role (CREATE ROLE DATA_ADMIN) :and grant update privileges to the role (GRANT UPDATE ON tbl TO :DATA_ADMIN). Finally, modify the "custom" application to issue a :SET ROLE DATA_ADMIN after connecting to the database using the :loginname. Now the user has update privileges, but these go away :once the connection is broken. You can keep the name of the role :secret so that the user cannot invoke update privileges through :a pass-through SET ROLE command. Yes. This is exactly what we are going to do in addition to using the security system in the Openlink ODBC drivers. This at least gives us some level of security. Far from ideal, but much better than nothing. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org