Uninstall

Central platform

To fully remove the KeySafe 5 application from your Kubernetes cluster, use helm uninstall. This uninstalls all KeySafe 5 Helm charts.

$ helm list --short --all-namespaces
keysafe5-backend
keysafe5-istio
keysafe5-ui

$ helm uninstall keysafe5-backend --namespace="nshieldkeysafe5"
release "keysafe5-backend" uninstalled

$ helm uninstall keysafe5-ui --namespace="nshieldkeysafe5"
release "keysafe5-ui" uninstalled

$ helm uninstall keysafe5-istio --namespace="nshieldkeysafe5"
release "keysafe5-istio" uninstalled

KeySafe 5 application data remains in your MongoDB database after uninstalling the application. To clear this data from the database, remove the databases defined by hsm_mgmt.dbName and sw_mgmt.dbName in the helm-keysafe5-backend chart.

KeySafe 5 agent

Before uninstalling the nShield KeySafe 5 agent, Entrust recommends that you back up any configuration files and certificates from the install.

Linux

To remove the KeySafe 5 agent from a Linux host run the KeySafe 5 uninstaller:

/opt/nfast/keysafe5/sbin/install -u

Then proceed to remove the following files and directories:

/opt/nfast/keysafe5
/opt/nfast/sbin/keysafe5-agent
/opt/nfast/lib/versions/keysafe5-agent-atv.txt
/opt/nfast/scripts/install.d/12keysafe5-agent
/opt/nfast/log/keysafe5-agent.log

The agent log file will be located in a different location if you have changed the default value of logging.file.path in the agent configuration file.

If required, you can also remove the keysafe5d user that was created as part of the installation.

Windows

To remove the KeySafe 5 agent from a Windows host:

Stop the KeySafe 5 agent service using Windows Service Manager.
Open the Control Panel and select Programs and Features.
Select the nShield KeySafe 5 Agent package.
Select Uninstall and follow the on-screen instructions.

To remove any configuration files, delete the %NFAST_DATA_HOME%\keysafe5 directory and remove the log file located at C:\ProgramData\nCipher\Log Files\KeySafe5-agent.log

The agent log file will be located in a different location if you have changed the default value of logging.file.path in the agent configuration file.