Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!nsc!voder!cullsj!gupta
From: gupta@cullsj.UUCP (Yogesh Gupta)
Newsgroups: comp.databases
Subject: Re: Restricting access to Informix tables
Summary: Grant execute authority on applications.
Message-ID: <585@cullsj.UUCP>
Date: 22 May 89 18:51:01 GMT
References: <1080@investor.UUCP> <1092@altos86.UUCP> <1347@infmx.UUCP>
Organization: Cullinet Software, San Jose, CA
Lines: 24

In article <1347@infmx.UUCP>, aland@infmx.UUCP (Dr. Scump) writes:
< In article <1092@altos86.UUCP> jon@altos86.UUCP (Jonathan Ma) writes:
< >In article <1080@investor.UUCP> news@investor.UUCP ( Bob Peirce) writes:
< >>We have a database we want to keep most people from updating or
< >>inserting except under controlled circumstances; ie, No from sperform,
< >>but YES from a 4GL data entry program.  
< >>-- 
< >>Bob Peirce, Pittsburgh, PA				 412-471-5320
< >	You can do the following as root:
< >	% cd $INFORMIXDIR/bin
< >	% chmod 500 sperform
< >
< 
< As I see it, a better route would be to be able to grant permissions
< to *applications*, like "Application Plans" in DB2.
< 
<     Alan S. Denney  @  Informix Software, Inc.    

Yes, that is extremely useful.  And you can do exaclty that with Cullinet's
Enterprise:DB.  It allows the owner of a program to grant EXECUTE authority
on a program, even though the person executing it might not have any other
authority.  Also, since our application builder generates applications
that are no different from user written applications, you can authorize
them similarly.