Basic Nshield Connect, Rfs And Client Configuration; About Nshield Connect And Client Configuration - Entrust nShield Connect Installation Manual

9. Basic nShield Connect, RFS and client
configuration
This chapter describes the initial nShield Connect, RFS and client computer configuration
steps. For more about:
• Security World Software installation and options, see
• Installing the optional nToken, see the nToken Installation Guide.
• The menu options, see
• Advanced nShield Connect and client configuration options, see the User Guide.
An installation will have only one RFS, but may have one or more
Clients. The RFS can also dual role as a Client. Before you can continue

with the following configuration, the RFS, and every Client must have
the Security World software installed, see

9.1. About nShield Connect and client configuration

An nShield Connect and a client communicate using their hardservers. These handle
secure transactions between the HSM within the Connect and any applications that run
on the client. You must configure:
• Each client hardserver to communicate with the hardserver of the nShield Connect
that it needs to use.
• The nShield Connect hardserver to communicate with the hardserver of the clients
that are allowed to use it.
Multiple nShield Connects can be configured to communicate with one

client, just as multiple clients can be configured to communicate with
one nShield Connect.
9.1.1. Remote file system (RFS)
Each nShield Connect must have a remote file system (RFS) configured. This includes
master copies of all the files that the nShield Connect needs. See the User Guide for your
HSM for more information about the RFS.
9.1.2. nShield Connect configuration
The current configuration files for the hardserver of an nShield Connect are stored in its
local file system. These files are automatically:
nShield® Connect Installation Guide
Top-level menu.
Installing the software.
Installing the software.
25 of 73