Adopted Authority and Client Server applications (Vance Stanley)

["Winkler, Marty" <MWinkler@xxxxxxxxx>]

message: 2
date: Thu, 13 Nov 2003 07:19:28 -0800 (PST)
from: Vance Stanley <w_vance_stanley@xxxxxxxxx>
subject: Adopted Authority and Client Server applications
  We are trying to implement a client server app that is using odbc to access 
the 400. The 400's
database is using adopted authority to handle security.  Is there another way 
other than an
additional authorization list to allow the client app. to update the 400?  
=====
W. Vance Stanley
Sr. Programmer Analyst
DEVON Houston, Texas
713-507-5536
-----------------------------
We use stored procedures and all production client access is done through 
these.  The Stored Procedure programs 
can then adopt whatever authority your normal production would use.  We use 
*autl and these programs are no different.
If the access is direct to your files, that is harder to do.  You might be able 
to use a supplemental group profile with whateer authority you need, but that 
usually becomes difficult when you want many different authorities for many 
different people.  If everyone (or just a few people) just wants to read all 
files...use the supplemental gorup to give them read only authority.  
Everything else can be done through the programs.

This may not cover everything, but is a good start.