IFS security

Use this Forum to post your “How to …” questions about your use of LongReach. This is not a technical support forum. Both the LongReach Support Team at LANSA and other LongReach customers may answer your questions. LANSA cannot guarantee the accuracy of any information posted by customers.
Post Reply
scooke
Posts: 1
Joined: Fri Jan 06, 2012 8:28 am

IFS security

Post by scooke » Fri Jan 06, 2012 8:43 am

Does anyone know how the security is handled? It appears that longreach is the owner. How does it know to separate the users?

alick
Posts: 67
Joined: Fri Dec 09, 2011 7:52 am

Re: IFS security

Post by alick » Fri Jan 06, 2012 10:39 am

Each user reads and writes to the IFS using their own user profile.

All files are tagged with CCSID 1208.

WRKLNK command and 8=Display attributes

Object . . . . . . : /longreachdata/user/ALICK/mydocument.txt
Type . . . . . . . . . . . . . . . . . : STMF
Owner . . . . . . . . . . . . . . . . : ALICK
Coded character set ID . . . . . . . . : 1208

When a file or folder is created it inherits authority from the parent folder.

To exclude public access or to allow other user profiles, edit the authority of the parent folder.

For example the top level folder for a LongReach user is

/longreachdata/user/{NAME}

where {NAME} is the signon profile name

If I set the authority of the folder for ALICK

/longreachdata/user/ALICK

Then all created child folders and files will inherit the authorities of this folder.

The LONGREACH user profile owns the LongReach server job and any access, log and trace files created by the server.

Post Reply