|
They all need the same authority.
Brings nothing to the party.
Big whoopie if one is only an inquiry while one is an actual update. I
cannot change SSA from *ALL to *USE for this file. I am not going to
create 10,000 user profiles to match each program.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/20/2016 02:11 PM
Subject: Re: program authority audit.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob,
IMHO, the better solution is
OWNER(*USRPRF) USEADPAUT(*NO)
on every program.
Thus, each program adopts the authority needed. Rather than depending on
authority to be passed down.
Regardless, you have to be careful if one of your infor program provides
access to a command line. That particular program you'd want OWNER(*USER)
USEADPAUT(*NO).
Charles
On Wed, Jan 20, 2016 at 1:59 PM, <rob@xxxxxxxxx> wrote:
Evaluating "program only access". This will allow only programs tomodify
data. The users may, or may not, continue to have "*USE" access to theset
data to facilitate queries.
In my understanding all this takes is some program near the top of the
chain to have USRPRF(*OWNER) and for all other programs in the chain to
have USEADPAUT(*YES).
For example, in an Infor shop you might have BPCSMENU owned by SSA and
to USRPRF(*OWNER). Infor does a fine job of using USEADPAUT(*YES) onall
of their remaining programs.run
So some user may have *USE to BPCSMENU. They could call that and then
Infor (providing their Infor security is set up right) to their heartsbe
content. However, even if they did have have access to a command line,
"Run SQL Scripts", etc they would not be able to use sql or anything to
modify the data. If the data is *PUBLIC *EXCLUDE or some such thing.
I realize that this has no bearing on stream file data and that has to
handled with profile handles.audit?
Now, I'd like to ensure that there are no programs that were modified to
have USEADPAUT(*NO).
Doesn't seem to be a DSPPGM MYLIB/*ALL capability to an outfile.
There's no such SQL service, is there?
There's no IBM supplied security audit, is there?
Am I down to a list api, and a program API or two, to perform this
list
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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.