iTP Secure WebServer System Administrator's Guide (Version 7.0)

Configuring the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-012
7-60
Adding WebSafe2 Internet Security Processors
(WISPs) to Your Configuration
Adding WebSafe2 Internet Security Processors (WISPs) to Your
Configuration
If you add WISPs to your configuration, you must add their IP addresses to
wid.config using an ip parameter in the following form:
ip = ip_address [TCP/IP_process]
If you want to use the default TCP/IP process $ZTC0, and $ZTC0 has been added to
the configuration of the subnet for the WISP you are adding, you do not need to
specify the TCP/IP process name.
All WISPs in a single iTP Secure WebServer environment must have the same
Superkey and Master File Key. Multiple WISPs can have the same or different
certificates; the configuration is simplest to manage if all WISPs use the same
certificate, stored in the file assigned to the keyfile parameter in wid.config.
The WID Configuration File
Example 7-5 illustrates the contents of a sample wid.config file.
Note. WISP is compatible only with systems running on G-series RVUs.
Note. WID is compatible only with systems running on G-series RVUs.
Caution. The wid configuration file used by keyadmin should not include extra white space
characters at the end of configuration parameters and should appear as in the sample file.