RE: Athuorization lists

["Fisher, Don" <dfisher@xxxxxxxxxxxxx>]

I just finished a major security project and one of the things I did was
eliminate all the authorization lists.  In my opinion, those things are a
maintenance nightmare, especially for a small shop.  

I changed the ownership of all objects in each of our applications to a
group profile for each application.  I then changed all the programs to
adopt the owner's authority.  The user's were given application specific
group profiles that allowed *USE access only to the programs, menus, and
commands.

So now if a user needs some access, we just add the appropriate group
profile to the user profile instead of searching for the correct
authorization list.  The group profile is easier since the user will be
requesting access like so and so has, which means inspecting so and so's
user profile will yield the correct group profile.  This is not so with
authorization lists. 

Hope that helps. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
Is there a clean way to keep up to date with authorization lists? We have
revamped some of our menus and would like to control who has access (*USE,
*ALL, etc. ) to the program objects and even some menus.

Some of the programs, workfiles, etc. would require authority to clear them,
etc. and I was wondering how some of the rest of you handle these types of
issues.

I know I can give a user authority to a secific object but is that the best
way to handle it or use authorization lists?
<clip>