A guide to nodekeys and how they are used to identify hosts
Each BoKS Manager host has a node key. The node keys are used to encrypt the security-related communication between BoKS hosts and for single sign-on using Telnet between Unix hosts.
You create node keys when you install BoKS Manager, BoKS Server Agent for Unix/Linux or BoKS Server Agent for Windows on a host. When the hosts are registered in the security database, you must type the node key again. The node key used at installation and the node key specified in the security database must be identical.
An exception to this is pre-registered hosts. You do not enter a node key for pre-registered hosts, instead they are assigned random node keys at install time that are automatically written to the BoKS database when BoKS Server Agent for Unix/Linux is installed on the host.
Note: The Master node key is automatically added to the database when the system is installed. See the BoKS Manager Installation Guide for information on how the node key is created during installation.
Personal computers with BoKS Desktop and BoKS SSH Client for Windows do not have node keys.
Note: In domains using Dynamic Host Configuration Protocol (DHCP), node keys must be unique for each host in order to avoid confusion between hosts with dynamic IP addresses.