Workflow Studio scoped application requirements for secure inputs

Adhere to the following scoped application requirements to implement secure (password2) inputs in your Virtual Agent topics.

You can add secure inputs to Virtual Agent topics in two ways:

• Create a secure custom input control that uses a Workflow Studio action or subflow with secure (password2 type) inputs.
• Add an Action utility node to a topic that refers to a Workflow Studio action or subflow that has a single password2 field as an input.

The Key Management Framework (KMF) must be installed and configured for your instance. The scoped application that uses the secure fields must also have the following:

• A sys_kmf_crypto_module record, with a related Symmetric Key Wrapping/Unwrapping sys_kmf_module_crypto_spec record
• A sys_kmf_crypto_caller_policy record with the following properties:
  • Policy name: <modify the auto-generated name>
  • Crypto module: com_glide_cs_glideencrypter
  • Type: Scope
  • Target Scope: <your application's scope>
  • Application: <the name of your scoped application>
  • Active: true
  • Result: Track
• A Workflow Studio action or subflow that accepts one or more password2 input fields

• A Script step in the Workflow Studio action that unwraps the password2/KMF passwords as follows:

  var op = new 
  sn_kmf_ns.KMFCryptoOperation("global.com_glide_cs_glideencrypter","SYMMETRIC_UNWRAPPING").withAlgorithm("AES").withOutputFormat("KMFNONE");
  var old_pw_clear_data = op.doOperation(inputs.old_pw);
  var new_pw_clear_data = op.doOperation(inputs.new_pw);
  var new_pw_confirmed_clear_data = op.doOperation(inputs.new_pw_confirmed);
  

For more information about password2 encryption with KMF, see Password2 encryption with KMF.

Parent Topic:Integrating Virtual Agent with Workflow Studio workflows