|
Home > |
|---|
Delete an existing SafeNet Network HSM server from the trusted list.
clientconfig deploy -server <hostname-or-ip> -client <hostname-or-ip> -partition <partition-name> [-password <string>] [-user <string>] [-regen] [-force] [-verbose]
| Option | Shortcut | Parameter | Description |
|---|---|---|---|
| -server | -n | <hostname-or-ip> | SafeNet Network HSM server hostname or IP address (mandatory). |
| -client | -c | restart | Client hostname or IP address (mandatory). |
| -partition | -par | <partition-name> | Partition name to assign to the client (mandatory). This is the name of a partition that must already exist on the HSM. |
| -password | -pw | <string> | Appliance admin role user's password. [See note, below] |
| -user | -ur | <string> | Appliance admin role user's name, (default is admin). [See note, below] |
| -regen | -rg | . | Regenerate new and replace existing client's certificate. |
| -force | -f | . | Force the action, no prompts. |
| -verbose | -v | . | Show verbose logs. |
Note: On a SafeNet Network HSM appliance, you can create users and assign them names that have meaning or utility in your organization, and then assign the named user a role. So, for example, instead of just one (default) appliance 'admin' user, you could have, say, "ShiftOneAdmin", "ShiftTwoAdmin", etc. Each such named user gets her/his own file-space on the appliance. So, in this command you are naming the user whose file-space will receive secure-copied certificates from clients, and you are providing that same user's password, so that this command can access the files in her/his filespace.
lunacm:> ccfg deploy -server mysa30 Server deleted mysa30 Command Result : No Error
lunacm:>