IBM High Performance Storage System HPSS Installation Manual page 286

High performance storage system
Hide thumbs Also See for High Performance Storage System HPSS:
Table of Contents

Advertisement

; 100MB = {
; BlockSize = 4MB
; StripeWidth= 0
; COS = 0
; }
; 1GB = {
; BlockSize = 8MB
; StripeWidth= 0
; COS = 0
; }
; }
# Use the System Password file routines (TRUE or FALSE)
# The Default for PFTP is FALSE (Case Sensitive!)
Use System Password Files = FALSE
#
Path and Name for the PFTP Password File
PFTP Password File = /var/hpss/etc/passwd
#
Path and Name for the PFTP Shadow Password File
# NOTE: PFTP does not currently use the value. It is used ONLY to
# change how the password is looked up! If the site is using
# /etc/passwd and the system running the PFTP Daemon utilizes
# some form of "Shadow" password file to authenticate PFTP users,
# this should be uncommented.
# Do NOT remove the part after the "=" sign.
;
PFTP Shadow File = /etc/security/passwd
#
Path and Name for the PFTP Group File
;
PFTP Group File = /etc/group
#
Primary Authentication Type for the FTP Daemon authentication
; Primary Authentication Mechanism = KRB5
#
Default: KEYTAB
; Primary Authenticator Type = KEYTAB
#
Default: /var/hpss/etc/hpss.keytab
; Primary Authenticator = /var/hpss/etc/hpss.keytab
#
Supported Client Authentication Mechanisms
#
This mechanism will be used to authenticate the FTP client
#
(end-user) with the FTP Daemon
#
Values: GSS, GSI, USER_PASS, IDENT
#
Default: USER_PASS &&
#
Mapfile Specifier specifies the type and required information
#
for Mapping one user name to another.
#
"FILE:", "LDAP:", and "DBAS:" The default type is "FILE:"
#
For "FILE:" specify the path and name of the file after the ":"
#
Default Authorization Mechanism specifies the location of the
#
pw_struct info.
#
"DBAS" is NOT currently supported.
#
This probably needs to be specified if a name mapping occurs.
#
Use Site Auth Method is used to specify that the USER_PASS Mode is
#
Overloaded and Hooks have been input to change the behaviour; e.g.,
#
USER_PASS will actually use a Crypto Card to Authenticate.
#
ONLY valid in the USER_PASS clause.
#
described: if this is specified for USER_PASS, it is impossible
#
to allow both username/password AND usename/CryptoCard
simultaneously.
Client Authentication Mechanisms = {
; GSS = {
; Mapfile Specifier = FILE:/var/hpss/etc/KRB2UnixMapfile
; Use Site Auth Method = KRB5KDC
; Default Authorization Mechanism = LDAP
; }
HPSS Installation Guide
Release 6.2 (Revision 2.0)
"Primary Authentication Mechanism"
This may be "UNIX", "LDAP", or "DBAS"
July 2008
The types include
NOTE: This is exactly as
This is
286

Advertisement

Table of Contents
loading

This manual is also suitable for:

Hpss 6.2

Table of Contents