HP Visualize J5000 hp enterprise file system: planning and configuring hp DCE/ - Page 151

Configuring a Client Without Enabling Remote Authentication

Page 151 highlights

The DFS/NFS Secure Gateway Configuring Gateway Server Machines Depending on how you configured your Gateway Server machines, configure each NFS client that is to provide access to DFS in one of the following ways: • If you configured your Gateway Servers so that users cannot issue the dfs_login command to authenticate to DCE, configure your NFS clients without enabling DCE authentication via the dfs_login command; follow the instructions in "Configuring a Client Without Enabling Remote Authentication." • If you configured your Gateway Servers so that users can issue the dfs_login command to authenticate to DCE, configure your NFS clients and enable DCE authentication via the dfs_login command; follow the instructions in "Configuring a Client and Enabling Remote Authentication." Because the steps in each of these sections mount /... on an NFS client, users who do not have DCE accounts can still use the NFS client for unauthenticated access to DFS. (See "Unauthenticated Access to DFS" for more information about unauthenticated access; see "Authenticated Access to DFS" for more information about authenticated access.) Configuring a Client Without Enabling Remote Authentication If you configured your Gateway Server machines so that users cannot issue the dfs_login command to authenticate to DCE, perform the steps in this section to configure your NFS clients. The steps enable DFS access from an NFS client without enabling DCE authentication from the client. Users can authenticate only via the dfsgw add command. To provide users of an NFS client with access to DFS but not the dfs_login command, perform the following steps on the client: 1 Log in as the local root user on the machine. 2 Mount the root of the DCE namespace, /..., on the machine. In the command, hostname is the hostname of a machine that exports /.... Each machine configured as a Gateway Server exports /.... When users access DFS from an NFS client, they go through the Gateway Server machine that exports /... to the client. To achieve proper load balancing if you configure multiple Gateway Server machines, ensure that the mounts of /... on your NFS clients are divided evenly among your Gateway Servers. (You can use the NFS automount mechanism with a direct automount map to mount /...; see your vendor's NFS documentation for more information.) 151

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164

151
The DFS/NFS Secure Gateway
Configuring Gateway Server Machines
Depending on how you configured your Gateway Server machines,
configure each NFS client that is to provide access to DFS in one of the
following ways:
If you configured your Gateway Servers so that users
cannot
issue the
dfs_login
command to authenticate to DCE, configure your NFS clients without enabling
DCE authentication via the
dfs_login
command; follow the instructions in
“Configuring a Client Without Enabling Remote Authentication.”
If you configured your Gateway Servers so that users
can
issue the
dfs_login
command to authenticate to DCE, configure your NFS clients and enable DCE
authentication via the
dfs_login
command; follow the instructions in
“Configuring a Client and Enabling Remote Authentication.”
Because the steps in each of these sections mount
/...
on an NFS client, users
who do not have DCE accounts can still use the NFS client for
unauthenticated access to DFS. (See “Unauthenticated Access to DFS” for
more information about unauthenticated access; see “Authenticated Access
to DFS” for more information about authenticated access.)
Configuring a Client Without Enabling Remote Authentication
If you configured your Gateway Server machines so that users cannot issue
the
dfs_login
command to authenticate to DCE, perform the steps in this
section to configure your NFS clients. The steps enable DFS access from an
NFS client without enabling DCE authentication from the client. Users can
authenticate only via the
dfsgw add
command.
To provide users of an NFS client with access to DFS but not the
dfs_login
command, perform the following steps on the client:
1
Log in as the local
root
user on the machine.
2
Mount the root of the DCE namespace,
/...
, on the machine. In the command,
hostname
is the hostname of a machine that exports
/...
.
Each machine
configured as a Gateway Server exports
/...
. When users access DFS from an
NFS client, they go through the Gateway Server machine that exports
/...
to
the client. To achieve proper load balancing if you configure multiple
Gateway Server machines, ensure that the mounts of
/...
on your NFS clients
are divided evenly among your Gateway Servers.
(You can use the NFS
automount mechanism with a direct automount map to mount
/...
; see your
vendor’s NFS documentation for more information.)