HP Workstation c3650 hp enterprise file system: planning and configuring hp DC - Page 140
Overview of the DFS/NFS Gateway
View all HP Workstation c3650 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 140 highlights
The DFS/NFS Secure Gateway Overview of the DFS/NFS Gateway Overview of the DFS/NFS Gateway The Distributed File Service/Network File System (DFS/NFS) Secure Gateway provides a mechanism for granting authenticated access to the DFS filespace from an NFS client. The DFS/NFS Secure Gateway allows users to access data in the DFS filespace from a machine that is configured as an NFS client but not as a DCE client. To use the DFS/NFS Secure Gateway for authenticated access to DFS, you must configure at least one Gateway Server machine. A Gateway Server machine must be a DFS client in the DCE cell to which access is to be provided. One function of a Gateway Server machine is to export the root of the DCE global namespace, /..., via NFS. On each NFS client from which users are to access DFS, you then mount /.... All users of the NFS clients then have unauthenticated access to DFS. The primary function of a Gateway Server machine is to provide DCE authentication to users of NFS clients. NFS users who have valid accounts in the registry database of the DCE cell authenticate to DCE to gain authenticated access to DFS. Depending on the needs of your users and the security considerations of your DCE cell, you can provide local authentication to DCE from Gateway Server machines, remote authentication to DCE from NFS clients, or both. Local and remote authentication work as follows: • Local authentication to DCE from Gateway Server machines is provided via the dfsgw add command. With local authentication, you can allow users to issue the dfsgw add command to authenticate themselves, or you can control access to DFS by allowing only system administrators to provide authentication via the dfsgw add command. (The dfsgw command suite includes additional commands to provide for central administration from Gateway Server machines.) Local authentication requires little configuration, but it provides a limited approach to authentication. Configuration consists only of installing the dfsgw commands on the Gateway Server machines. However, authentication requires either administrative intervention or remote access to the Gateway Server machine (for example, via the telnet program); the latter approach results in user passwords being sent over the network in the clear. 140