If you are on V7R3 you can use the new security collection features to see
how the system resolved the security with the Authority Collection support.
Once you have that in the file a simple SQL statement should pull the
records for you.
Alternatively, you can use the security audit journal to pull the
appropriate records. (Any level of OS)
I can confirm that NFS will ONLY use UID/PID in the connection, so it is
compliant with other systems (Unix based) standards. Been that way for many
years, going back in the V4 days.
That's why when folks migrate from system to system, if you use those tools,
it's really important to maintain the UID/PID/User profile relationships.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Mitchell,
Dana
Sent: Monday, November 19, 2018 8:23 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: NFS security
So far our attempts to verify that this works this way have failed. Is
there any messages anywhere that would indicate if a match was found and
used? Any other diagnostic data available?
Dana
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vernon Hamberg
Sent: Friday, November 16, 2018 6:13 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: NFS security
NFS always uses UID or GID (I think) - no matter the platform it's running
on.
On 11/16/2018 2:52 PM, Mitchell, Dana wrote:
Is there any doc or wisdom that explains better how to secure directories
between two IBM I systems with an NFS export/mount.
Attention: This electronic document and associated attachments (if any) may
contain confidential information of the sender (SHAZAM Network) and is
intended solely for use by the addressee(s). Review by unintended
individuals is prohibited. If you are not the intended recipient: (i) do not
read, transmit, copy, disclose, store, or utilize this communication in any
manner; (ii) please reply to the sender immediately, state that you received
it in error and permanently delete this message and any attachment(s) from
your computer and destroy the material in its entirety if in hard copy
format. If you are the intended recipient, please use discretion in any
email reply to ensure that you do not send confidential information as we
cannot secure it through this medium. By responding to us through internet
e-mail, you agree to hold SHAZAM, Inc. and all affiliated companies harmless
for any unintentional dissemination of information contained in your
message. Thank you.
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
