Flow Designer scoped application requirements for secure inputs
-
- UpdatedAug 3, 2023
- 1 minute read
- Vancouver
- Virtual Agent
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
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 Flow Designer action or subflow with secure (password2 type) inputs.
- Add an Action utility node to a topic that refers to a Flow Designer 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 Flow Designer action or subflow that accepts one or more password2 input fields
- A Script step in the Flow Designer action that unwraps the password2/KMF passwords as follows:
For more information about password2 encryption with KMF, see Password2 encryption with KMF.