Set table access restrictions on ODBC-user level 1

[dirkg]

Hello,

I have never created an ODBC-user myself on for instance an Oracle database, but I would like to convince my client to set up an ODBC-connection to his database in order to have easy access to the data. However with all the ODBC-connections I've seen, I could always access all the tables in the database which is a serious concern for my client. Therefore I would like to know whether it is possible to restrict access for an ODBC-user to only a few specified tables of the database on which the ODBC-user is created.

Thanks a lot in advance for your help.


Greetings,


Dirk

dirk.news@yucom.be

 

[foxdev]

with all the ODBC-connections I've seen, I could always access all the tables in the database

This is an issue with rights on the database, not ODBC, and should be handled there (by setting the database permissions). Why?

A) security rights should be set at the most trustworthy and reliable level, and in this case it is the database;
B) I've never seen an ODBC driver that lets you set security access at the ODBC/DSN level. Not to say it doesn't exist, but I haven't seen it in the SQL Server, Sybase, and Oracle drivers I've used.

So the answer to your dilemma is simple:
Have the database owner create a new user for access via your desired technique (ODBC, for example), and allow only the appropriate rights for that user. Robert Bradley

http://www.lowcostprints.com

http://www.foxdev.com

 

[dirkg]

thanks, that was what I wanted to know!
So I guess for an Oracle database the possibilities ti assign user permissions are more or less working as in an Access database or is it a lot more complicated?

Greetings,


Dirk

 

[foxdev]

Well, Dirk, my experience is the opposite of yours: I know very little about MS Access, so I don't know how to compare it to Oracle or other database servers.

Generally, you can specify which tables a user can access, as well as what actions (Insert, Update, Delete, Select) a user can perform on each of those tables. You can also set permissions on stored procedures and views.

One technique to control security is to remove all rights from the tables, and grant rights to stored procedures or views for access to the tables. -----------------
Robert Bradley
use coupon code "TEKTIPS" for 15% off at:

http://www.lowcostprints.com

http://www.foxdev.com