Paul, I just create a user group with the following access profile and I can only "read" the scan results in the "ilmt/output" directory.
*/*/file/local?Directory=ilmt&Access=r
*/*/login/ssh?Access=r+w+a+d+x
*/*/login/web-mgmt?Access=r+w+a+d+x
*/*/system/ilmt-force-scan?Access=r+w+a+d+x
*/*/system/ilmt-scanner?Access=r+w+a+d+x
This profile allow the users in this group to log in to the GUI or CLI and work with the ILMT artifacts. I didn't state to "default" domain, but this is where all these resources reside and will not change permission/access. What I did note and why I added CLI access was that the GUI always shows no files (a bug that you need to open a service ticket against).
When you use the CLI, this is what I get for for this user in this group.
# co
Global mode
(config)# dir local:
% Access Denied - use 'cancel' to exit any submode.
(config)# dir local:///ilmt
% Access Denied - use 'cancel' to exit any submode.
(config)# dir local:///ilmt/output/
File Name Last Modified Size
--------- ------------- ----
202301101619-<systemname>-1673345956.tar.gz Jan 10, 2023 11:19:03 AM 3489
8661.6 MB available to local:///ilmt/output/
Note that I find that not showing the subdirectories is also a bug, but it might be working as designed/implemented.
With all stated, I believe what Paul is attempting to state is that you can probably create a script that anyone can run. I've seen done similar with simple PHP, but this was for a custom web service that does all activities and any type of script can be used. Any user with access to this script run it (as PHP, it's a button on a web page). The script contains the credentials for the DataPower user (who can have full access but isn't the person who clicked the button). The script can do the following if created correct.
- Copy the scan files from DP (local:///ilmt/output/*) to a remote server with same file name.
- Upload these files from the remote server (because you still need to keep copies for 2 years) to the configured location on the ILMT server.
- Delete these files from DP.
Basically Paul is stated that the person who runs the scripts doesn't know credentials for the DP user and the DP user can have access to more that what the person running the script ever needs to know.
------------------------------
F Hackerman
------------------------------