RE: Security and the ODBC
set role appl;
select count(*) from wippage@hospital4:t600_wip_page;
Doesn't work. I'm connected to database mris_prd and this database has
a role called appl. The wippage@hospital4 has no rights to public and
only understands the appl user and appl role. You cannot select data
from wippage@hospital4:t600_wip_page unless that database has public
access or your original access. You get
387: No connect permission.
111: ISAM error: no record found
Now the mris_prd database is fooled by the role, but all of the others
are wide open:-(
-----Original Message-----
From: Dave Otto [SMTP:dotto@themoneystore.com]
Sent: Tuesday, September 09, 1997 4:27 PM
To: Tim Kelly
Cc: informix-list@rmy.emory.edu
Subject: RE: Security and the ODBC
At 01:06 PM 9/9/97 -0400, Tim Kelly wrote:
>Now that's what I'm taking about. Now it appears I'm not
overlooking
>some feature to CLI Informix etc. Matter of fact the 2.x ODBC
>specification doesn't call for anything like this. I also have
the same
>issue with MS SQL-Server and Oracle.
What was described here could quite simply be implemented w/
roles.
First revoke all access rights from everyone (including public).
Then
set up the roles you need to run the application. The "set
role" should
be the first command issued from the application.
-d