Changing master keys to ensure data security

About master keys

ContentDirector uses a master key file at both ends of each data transfer to authenticate the identity of the sender and receiver. The installation process creates a default master key on the core application and destination machines.

For more secure content distribution, you can create a new, unique master key for your ContentDirector network. The process consists of the following steps:

Generating the new master key at the core application
Activating the new master key at the core application
Transferring the new master key to destinations

How the process works

You create a master key through the Tools menu of the management console. When you do so, the core application generates a new master key with the name master_key_new <digits>, and places it in the config directory of the core application directory.

When you create a master key, it does not become the current key automatically. To function, the master key file must be renamed master_key on the core application and the transport group leaders and group members. After the new key is renamed master_key on the core application machine, it becomes the operative key and no content distribution can take place until the new key is transferred to the group leaders on the destination devices and is renamed master_key.

The method you use for transferring the new master key to destinations depends on the destination type and the degree to which security is a concern:

For destinations where security is not a primary concern, you can use the NetCache Manager utility to transfer the master key.
For destinations where security is a primary concern, you can copy the new master key from the core application server to a diskette and deliver it manually.