iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Integrating the WebSafe2 Internet Security
Processor (WISP)
iTP Secure WebServer System Administrator’s Guide—522659-001
5-6
If You Are Upgrading the WebSafe2 Internet Security
Processor (WISP) From An Earlier Version
7. Complete the quickstart procedure to verify installation and configuration.
See Verifying Integration of a WebSafe2 Internet Security Processor (WISP)
on
page 5-15.
If the server has been operating, it will have to be restarted before configuration
changes take effect.
If You Are Upgrading the WebSafe2 Internet Security Processor
(WISP) From An Earlier Version
If you are upgrading your WISP firmware from version 2.4 or earlier to version 2.5 or
later, you must contact your Atalla representative to convert your hardware key database
to a new version of the Atalla Public Key Block (APKB) format.
Installing the WebSafe2 Internet Security Processor (WISP)
Refer to the WebSafe2 Internet Security Processor Installation and Operations Guide for
the procedures required to set up and initialize the WISP. The following tasks are
particularly relevant to integrating the WISP into the iTP Secure WebServer
environment:
•
Assigning an IP address to each WISP. You use the SCT to assign the address: use
the Set IP Address command to assign an IP address and the Get IP Address to
verify the address you entered. After you have verified the IP address, you must turn
the WISP off and on again before using it in a WebServer configuration.
•
Loading the Superkey and the MFK into each WISP. You use the SCT to create
these keys and to load them into the WISP.
•
If you intend to use SSL 3.0 services with the WISP, you need to install the latest
version of the WID. See Installing the WebSafe2 Interface Driver (WID)
on
page 5-7 for specific information.
Preparing a Distinguished Name (DN) for the Certificate
Use the instructions in Formatting Distinguished Names (DNs) on page 4-4 to prepare a
DN for the Certificate you will obtain. You will use this DN when you configure and
generate a public/private key pair.
Note. All WISPs in a single iTP Secure WebServer environment must have the same
Superkey and MFK. Multiple WISPs can have the same or different certificates; however,
the configuration is simplest to manage if all WISPs use the same certificate.