Issue Summary

When adding a script to the list of allowlisted scripts for Assets automation, the system doesn't check and correct for any spaces or other invalid characters in the path

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Go to the configuration cog > Manage apps > Assets allowlist and click Edit settings
2. In the file path field enter in the path of a valid groovy script, but add a space at the beginning of the path
3. Click Add script to allowlist
4. Note that there is no error, and that the leading space in the path is not displayed in the list of allowed scripts once added
5. Create an Assets schema and go to its configuration
6. Go to the Automation tab and create an automation which will execute the allowlisted script upon an object being created
7. Edit an object

Expected Results

The object should be updated as per the instructions in the groovy file.

Actual Results

Because the allowlisted path in the Assets configuration included a leading space, the system doesn't think that the script in the automation rule matches it and so the script isn't run

The below exception is thrown in the "insight_automation.log" file:

2023-11-20 04:04:26,971 [insight-event-0] | Execute Rule action (AutomationRuleGroovyScriptAction): Start, id: 1, event [id: 1, iql: No iql], condition: None
2023-11-20 04:04:26,973 [insight-event-0] | GroovyScriptAction, got absFilePath: /home/ubuntu/jira/test2.groovy
2023-11-20 04:04:26,977 [insight-event-0] | GroovyScriptAction, not in whitelist, exit, absFilePath: /home/ubuntu/jira/test2.groovy

Workaround

Currently there is no known workaround for this behavior other than to check that your allowlist paths do not contain any leading or trailing spaces or other characters. A workaround will be added here when available

This behaviour is observed in the 4.20.x versions up to the newest release available as of this bug report; 5.11.3.