The client has their majority of their scripts that they would use in the A2A configuration as Powershell scripts. Currently the powershell scripts will not be able to authorize powershell scripts based on script name (this is the feature that hashes the script and will not allow A2A to work if that script has been modified). You can, however, authorize other scripts on the Windows OS based on other scripting languages such as Perl, Python.
The client would like to authorize the script based on the name, along with the hash integrity fee to be used. Can this Powershell support feature be implemented in a future release?