Skip to main content

Generating a system identity for axesFlip licensing

Before axesFlip can be activated, a system identity must be generated and provided to axes4. This system identity is used to create the token required for using axesFlip deployment options.

The system identity is generated using the axesFlip CLI. However, the exact command depends on your environment and deployment scenario. Therefore, customers must first contact axes4 to obtain the correct command.

Important: Do not create your own command. Always use the command provided by axes4, as different systems may require different identity parameters.


Process overview

  1. Contact axes4 and request a system identity generation command.
  2. axes4 determines the appropriate identity parameters for your environment.
  3. axes4 provides a customized axesFlip CLI command.
  4. Execute the provided command on the target system.
  5. Send the generated JSON file back to axes4.
  6. axes4 generates your token.
  7. Use the received token to activate axesFlip.

Prerequisites

Before generating the system identity, ensure that:

  • You have downloaded the axesFlip package, which includes the axesFlip CLI: Download axesFlip
  • You have access to the target system where axesFlip will be deployed.
  • You have received a system identity generation command from axes4.

Generate the system identity

Run the exact command received from axes4.

Example

The following example includes a device fingerprint and MAC address and saves the generated system identity to binding.json:

create-system-info-binding \
--include-device-fingerprint \
--device-fingerprint-factors 1234 \
--include-mac-address \
--output-file binding.json

Note: This is only an example. The command provided by axes4 may differ depending on your environment and deployment requirements.

If the command completes successfully, a JSON file containing your system identity will be created.


Command parameters

The create-system-info-binding command supports the following parameters:

  • -h, --help
    Displays command help and usage information.
  • -d, --include-device-fingerprint
    Includes a device fingerprint in the generated system identity.
  • -f, --device-fingerprint-factors
    Specifies the device fingerprint factor provided by axes4. Required when --include-device-fingerprint is used.
  • -m, --include-mac-address
    Includes the system's MAC address in the generated system identity.
  • -a, --include-active-directory-domain-sid
    Includes the Active Directory Domain SID in the generated system identity.
  • -o, --output-file
    Saves the generated system identity as a JSON file at the specified path.

Example output

The generated system identity may look similar to the following:

{
   "version": "1.0",
   "clientActivationTime": "2026-07-07T07:34:48.126185Z",
   "clientOperatingSystem": "Microsoft Windows NT 10.0.26200.0",
   "systemIdentity": {
      "deviceFingerprintFactors": 1234,
      "deviceFingerprint": "0123456789XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
      "domainSid": null,
      "macAddress": "0123456789XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
   }
}

 The values shown above are examples only and will differ for each system.


Send the information to axes4

After generating the system identity, send the information back to axes4.

Preferred method: JSON file

If the command was executed with the --output-file option, send the generated JSON file to axes4.

This is the preferred method because it preserves the complete system identity information exactly as generated.

Alternative method: console output

If an output file was not created, you may copy the JSON output displayed in the console and send it to axes4.

While this method is supported, providing the generated JSON file is recommended whenever possible.


Next steps

After axes4 receives your system identity information, a token will be generated and returned to you.

Once the token has been provided, you can proceed with the activation and deployment of axesFlip according to your selected deployment option.