Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Restrict ftpuser ?
7 views
Skip to first unread message
Silenus paparias
Dec 13, 2011, 7:05:51 AM12/13/11
to
How to restrict a ftp-user to work (get,put files) ONLY in a library
named T24LIB?
This user should do nothing else on System or in other LIBS..
All users LIBs are with Authority *Public CHANGE.
(Users are restricted through Menu)
Must i for each Lib separate include the FTP user as *EXCLUDE?
or a simple way there ?
thanks.
PS: The Ftp user are simple *user with no Special Authorities.
named T24LIB?
This user should do nothing else on System or in other LIBS..
All users LIBs are with Authority *Public CHANGE.
(Users are restricted through Menu)
Must i for each Lib separate include the FTP user as *EXCLUDE?
or a simple way there ?
thanks.
PS: The Ftp user are simple *user with no Special Authorities.
CRPence
Dec 13, 2011, 2:25:19 PM12/13/11
to
On 13-Dec-2011 04:05 , Silenus paparias wrote:
> How to restrict a ftp-user to work (get,put files) ONLY in a library
> named T24LIB?
> This user should do nothing else on System or in other LIBS..
> All users LIBs are with Authority *Public CHANGE.
> (Users are restricted through Menu)
> Must I for each Lib separate include the FTP user as *EXCLUDE? or a
> How to restrict a ftp-user to work (get,put files) ONLY in a library
> named T24LIB?
> This user should do nothing else on System or in other LIBS..
> All users LIBs are with Authority *Public CHANGE.
> (Users are restricted through Menu)
> simple way there ?
>
> PS: The Ftp user are simple *user with no Special Authorities.
The best answer is to implement object security instead of depending
on menu-based security since the latter is valid only for when the only
access by a user is ensured to be via [effectively interactive] 5250
sessions.
Without that...
The FTP server enables a registered exit which can handle
restrictions at the server. There are even sample programs. Visit the
InfoCenter for your release. Following a model of establishing an
"anonymous FTP" might parallel your needs, forcing the FTP server to
operate under a specific limited-authority user; e.g. the user under
which the FTP server processing operates irrespective of the origin of
the request, is authorized only to the *LIB T24LIB.
A client FTP request could be limited to a "scripted" request which
could generate the input file which is authorized only to the program
performing a "batch FTP", and created in QTEMP to preclude visibility to
a stored password; the program can validate the restrictions for any
dynamic naming. Search the Web for the two tokens FTPAPI and Klement
for another means for another programmed means as client for which
standard input is not required for scripting.
Regards, Chuck
0 new messages