Marco,
Please submit this as an Ideation:
https://community.broadcom.com/ideation/allideas. That is where the developers look for customer suggestions as they lay out the product roadmap.
I like where your going with this...
#1 should be doable, and I agree it's annoying.
I can see the value in #2... often a script or application is not a standalone entity and having the ability to confirm that all of the related files have not been tampered with makes a lot of sense.
Post a link to you ideation here when you have created it and I'll add a vote.
Original Message:
Sent: 11-20-2020 02:42 AM
From: Marco Siviero
Subject: Enhancement for A2A script management
Hello,
at the moment if we launch an A2A script in Windows OS we are forced to explicit the interpreter in front of it (example: powershell C:\temp\script.ps1), and PAM is able to check integrity file of only one script launched.
We would like to suggest one of these changes (or both if you can):
- We would like to have the possibility to run the script without specifying the interpreter (example:
PS> C:\temp\script.ps1
or
$var = C:\temp\script.ps1)
- We would like PAM to be able to check the integrity not only of the script launched but also of a library (or more than one).
Or, alternatively, allow the execution of the A2A script only if the integrity of the script is combined with that of a library / DLL that works with it.
Thanks.