appid set
Set an application access ID on the HSM. Application IDs are assigned as a way of sharing login state among multiple processes. AppIDs require two 4-byte/32-bit unsigned integers, one designated "major" and the other designated "minor". After setting an appid, you must open it using appid open to allow your applications to use it to access the HSM. Once you set an appid you can open and close it, as required, to allow or deny application access to the HSM using the appid. For a full description of application IDs, see Application IDs.
NOTE If you are concerned that an unauthorized process might be able to take over a login state, then you can use large, difficult-to-guess numbers for the major and minor appids. If this is not a concern, or for use in a development lab, you can use any arbitrary, conveniently small integers.
This command is not applicable on DPoD Luna Cloud HSM services.
NOTE From HSM firmware version 7.8.4 onward, Application IDs (APPId) are encrypted, with the following effects:
•Whenever firmware is upgraded from a non-APPID encrypted version (before firmware 7.8.4) to an encrypted APPID firmware version, the access ID shown in the logs will change.
•After the new firmware starts, the encrypted value of the same access ID for that application (for example, LUNACM) is now shown.
•The access ID shown also changes after every reset/restart of firmware version 7.8.4 onward because a new APPID encryption key (AEK) is created each time firmware starts up. The AEK is used by the crypto library of the APP to encrypt the access ID.
•Also whenever an Application is started it creates a new random access ID each time (unless fixed to a value [set AppId= under the Misc section] in the Configuration file ).
Syntax
appid set -major <value> -minor <value>
| Argument(s) | Shortcut | Description |
|---|---|---|
| -major <value> | -ma | The major appid. |
| -minor <value> | -mi | The minor appid. |
Example
lunacm:> appid set -major 1 -minor 40 Command Result : No Error
