This system requires that specific fields in the token request body be encoded or encrypted before being sent. This example demonstrates both techniques applied to different fields: the username is base64-encoded, and the password is AES-encrypted.
Both techniques operate on the field’s value only — the key name is never encoded or encrypted.
This scenario requires only a change to the request schema file. For background on these schema flags, see Encode a field value and Encrypt a field value.
encode: true on the username field to base64-encode its value before the request is sent.encrypt object with type and key to the password field to AES-encrypt its value. Encryption only applies when a key is provided. Currently, AES is the only supported encryption type.