Page History

...

The JS7 allows to operate JOC Cockpit in one of the security levels Security Levels low, medium, high, for details see JS7 - Security Architecture.

• low: workflows are digitally signed from a single private key Private Key used by all user accounts in JOC Cockpit. The key Private Key is stored in the JS7 database.
• medium: workflows are digitally signed from private keys Private Keys per user accounts in JOC Cockpit. The key Private Key is stored in the JS7 database.
• high: workflows have to be digitally signed outside of JOC Cockpit. Users export workflows from the JS7 inventory to a .tar.gz/.zip export archive.

...

openssl dgst -sha256 -sign c:\tmp\sos.private-ec-key.pem -out c:\tmp\example-wf.workflow.json.sig.bin c:\tmp\example-wf.workflow.json

• -sha256
  • the The signer algorithm
• -sign c:\tmp\sos.private-ec-key.pem
  • the private key The Private Key file used to sign the workflow file
• -out c:\tmp\example-wf.workflow.json.sig.bin
  • the The path to the output file that contains the binary representation of the signature
• c:\tmp\example-wf.workflow.json
  • the The path to the original workflow file.
    
    
    

...

• base64
  • OpenSSL switch to transform the signature file from binary encoding to base64 encoding
• -in c:\tmp\example-wf.workflow.json.sig.bin
  • the The binary encoded signature file as created in step 1)
• -out c:\tmp\example-wf.workflow.json.sig
  • the The base64 encoded signature file to be created that carries a .sig extension and that will be picked up later on by JOC Cockpit when importing workflows and signatures.

...