9 Basic nShield Connect, RFS and client configuration
9 Basic nShield Connect, RFS and
client configuration
This chapter describes the initial nShield Connect, RFS and client computer configuration steps. For
more about:
l Security World Software installation and options, see
Installing the software
on page 24
l Installing the optional nToken and software, see the
nToken Installation Guide
l The menu options, see
Top-level menu
on page 35
l 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
Installing the software
on
page 24.
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:
l Each client hardserver to communicate with the hardserver of the nShield Connect that it needs to
use.
l 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 HSMfor more information
about the RFS.
nShield® Connect - Installation Guide
Page 40
To Next Page