|
One option I would recommend would be to have the group profile of the adminstrator own profiles to avoid cleanup nightmares down the road. We have utilized a application owning concept where all userids whether it be a group or regular userid are owned by a single 'Owning Profile'. This allows us to apply the same concept to the applications. One profile to owns the data, another owns the programs or objects. Exclude everyone from the data via an authorization list. Have your programs adopt authority with *OWNER and use groups and authorization lists to grant access to programs. Thanks, Tony Quixtar, Inc. Sr. Systems Support Specialist phone: 616-787-8507 fax: 616-682-4232 email: tdeller@quixtar.com "Phil" <sublime78ska@yahoo. To: <security400@midrange.com> com> cc: Sent by: Subject: RE: [Security400] user profile question security400-admin@mi drange.com 08/21/2001 03:14 PM Please respond to security400 > > Honestly, I don't think it really matters who owns the user profiles. > Until the guy who created most of the user profiles quit, and you want to delete his user profile. I worked for a software vendor where all the objects were owned by a programmer, and that same user profile existed on a target system. On restore, instead of the objects becoming owned by qdftown, they kept ownership. Then the guy at the customer site quit, and they selected to delete objects owned by him. Wasn't pretty. Phil _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ This is the Security Administration on the AS400 / iSeries (Security400) mailing list To post a message email: Security400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/security400 or email: Security400-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.