|
|
|
|
|
Scripts which include sensitive information such as User passwords may be saved as .pfz files which are encrypted at rest.
Saving (and encrypting) and Loading (and decrypting) encrypted scripts in the script editor requires Write permission for Company > Scripts > Encrypted, in addition other scripting permissions.
Executing encrypted scripts requires at least Read permission for Company > Scripts > Encrypted, in addition other scripting permissions.
The SetPermUser function which may be used to temporarily raise the permission level at which the script is executing may only be called in an encrypted script.
This would usually be used where an event script executes, e.g. an AfterSave event, and the script requires access at a higher permission level than the logged in user.
When an encrypted script completes the permission level is returned to that of the logged in user.
The SetPassword(Password as String) and SetSMTPPassword(Password as String) methods on the System and Company User objects may only be called in and via encrypted script when the dataset is in edit mode.
Encryption is also recommended when the Login or SystemLogin functions are used since Passwords must be included.