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

Authenticated Access to DFS

Page 155 highlights

The DFS/NFS Secure Gateway Configuring Gateway Server Machines • For objects in non-LFS filesets, unauthenticated users receive the permissions granted by the other mode bits of the object. • For objects in DCE LFS filesets, unauthenticated users receive the permissions granted by the any_other entry, if it exists, on the ACL of the object. The mask_obj entry filters permissions granted via the any_other entry. When an unauthenticated user creates an object, the object is owned by the user nobody and the group nogroup. The UID of the user nobody is -2, and the GID of the group nogroup is also -2. (Note that identities and ID numbers of an unauthenticated user and group can vary between systems; see your vendor's documentation for more information.) Unauthenticated access is provided with the DFS/NFS Secure Gateway as a side effect of configuring Gateway Server machines and NFS clients. Unauthenticated access is available without the DFS/NFS Secure Gateway. Simply export /... from a DFS client that is also an NFS Server, and mount /... on each NFS client from which users are to access DFS. Authenticated Access to DFS Authenticated access is available to users who have accounts in the DCE cell. When an authenticated user accesses an object in the DFS filespace, the user receives the permissions associated with the DCE identity to which the user is authenticated. When the user creates an object, the object is owned by the user and the user's primary group. To authenticate to DCE, you can issue either of the following commands, both of which establish credentials recognized by the DCE Security Service: • From an NFS client, enter the dfs_login command. (See "Authenticating to DCE from an NFS Client.") • From a Gateway Server machine, enter the dfsgw add command. (See "Authenticating to DCE from a Gateway Server Machine.") A user who desires authenticated access to DFS must have a principal and account in the registry database of the DCE cell. An entry must exist for the user in the /etc/passwd file on the machine configured as a Gateway Server and on each NFS client from which the user is to access DCE. The user's UID in the /etc/passwd file must match the user's UID in the DCE registry 155

  • 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

155
The DFS/NFS Secure Gateway
Configuring Gateway Server Machines
For objects in non-LFS filesets
, unauthenticated users receive the permissions
granted by the
other
mode bits of the object.
For objects in DCE LFS filesets
, unauthenticated users receive the
permissions granted
by the
any_other
entry, if it exists, on the ACL of the
object. The
mask_obj
entry filters permissions granted via the
any_other
entry.
When an unauthenticated user creates an object, the object is owned by the
user
nobody
and the group
nogroup
. The UID of the user
nobody
is
-2
, and
the GID of the group
nogroup
is also
-2
. (Note that identities and ID
numbers of an unauthenticated user and group can vary between systems;
see your vendor’s documentation for more information.)
Unauthenticated access is provided with the DFS/NFS Secure Gateway as a
side effect of configuring Gateway Server machines and NFS clients.
Unauthenticated access is available without the DFS/NFS Secure Gateway.
Simply export
/...
from a DFS client that is also an NFS Server, and mount
/...
on each NFS client from which users are to access DFS.
Authenticated Access to DFS
Authenticated access is available to users who have accounts in the DCE
cell.
When an authenticated user accesses an object in the DFS filespace,
the user receives the permissions associated with the DCE identity to which
the user is authenticated. When the user creates an object, the object is
owned by the user and the user’s primary group.
To authenticate to DCE, you can issue either of the following commands,
both of which establish credentials recognized by the DCE Security Service:
From an NFS client, enter the
dfs_login
command. (See “Authenticating to
DCE from an NFS Client.”)
From a Gateway Server machine, enter the
dfsgw add
command. (See
“Authenticating to DCE from a Gateway Server Machine.”)
A user who desires authenticated access to DFS must have a principal and
account in the registry database of the DCE cell. An entry must exist for the
user in the
/etc/passwd
file on the machine configured as a Gateway Server
and on each NFS client from which the user is to access DCE. The user’s
UID in the
/etc/passwd
file must match the user’s UID in the DCE registry