Why Regenerate Security Keys?

The security keys used by the N1 System Manager must be identical across all servers. Under normal operation, the security keys used by the keys can be left in their default configuration. You might have to regenerate security keys from time to time:

• If there is a risk that the root password of the management server has been exposed or compromised, regenerate the security keys.

• If the system date on the management server has been changed using the date command, regenerate the security keys. If the system date on the management server has been changed using the date command, there is a risk that the next time the N1 System Manager management daemon, n1sminit, is restarted, no services are subsequently provided by the management server. In this case, keys must be regenerated, and the N1 System Manager management daemon restarted, as explained in How to Regenerate Common Agent Container Security Keys.

How to Regenerate Common Agent Container Security Keys

Steps

1. On the management server as root, stop the N1 System Manager management daemon.

   # /etc/init.d/n1sminit stop

2. Regenerate security keys using the create-keys subcommand.

   If the management server is running Linux:

   # /opt/sun/cacao/bin/cacaoadm create-keys --force

   If the management server is running the Solaris OS:

   # /opt/SUNWcacao/bin/cacaoadm create-keys --force

3. As root on the management server, restart the N1 System Manager management daemon.

   # /etc/init.d/n1sminit start