Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Download sample workflow (upload .json): pduVariableCrypto.workflow.json

First Job: encrypt-variables

The fist job encrypt-variables looks like this:

...

  • The job makes use of JS7 - Script Includes: the Crypto Script Include holds the Shell functions used in the job.
    • The ##!include Crypto inserts the shell code available from the indicated Crypto Script Include.
    • The Script Include is invoked once per job and can be parameterized to specify the location of the public key.
      • ## include Crypto --replace="<public-key>","/var/sos-berlin.com/js7/agent/config/agent.pub"
      • The above value represents the default value that will be used if the Script Include is invoked without replacement options.
  • The EncryptVariable shell function expects the name of the variable and the value that should be encrypted.
    • EncryptVariable <name> <value> [<key-name> [,<public-key>]]
      • <name>: The name of the variable is required.
      • <value>: The value of the variable is required.
      • <key-name>: The name of a second variable holding the encrypted symmetric key. Defaults to <name>_key.
      • <public-key>: The path to the public key file is specified. Defaults to <agent-data>/config/agent.pub.
    • The shell function will encrypt the variable with the public key.
    • The encrypted variable will be forwarded to subsequent jobs and instructions in the workflow.

Second Job: decrypt-variables

The second job decrypt-variables looks like this:

...