|
> I must admit that this thread has definitely got me to thinking > twice (or even more times than that) with our present security procedure. > > In revisiting this particular e-mail, a couple of questions have > come to mind. > Q1 - "- maintaining object authorities requires special care when database > changes are done.". Can you please expand on this statement. We > have done a few database changes, with object authorities in > place, and have had no problems. However, the question that comes > to mind is, for any future changes, could we be missing something? > With CHGPF this has become easy, but previously you had to apply all authority changes each time you recreated a database file (e.g. after adding new fields) > Q2. Before it was decided to apply object authority as the > procedure to use, one of the options considered was using > adopting authority, with the application being the deciding > factor. You mention "user groups defined in our "menu system",", > How are these groups linked to a User Profile, is it through the > operating system,. or strictly as part of the application. If it > is part of the application, how is deleting a User Profile > handled so that the particular profile name is also deleted from > the application derived user groups? > The user groups in our system is defined strictly as a part of our application, but the user profile must exist (and must be "defined" in the "menu system"). We create (and delete) user profiles in our "menu system" (or service system as we call it), but you can specify exit programs (wrkreginf) to be called when user profiles are created/changed/deleted. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@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.