Open joeyhenkel opened 7 years ago
@Compl3teSle3t there was no calling script or config file. It was mainly designed to be cmdlet-driven, with all input via parameters. These scripts were pretty specific to my organization's needs, so some of it might be confusing. If you have any specific questions, please feel free to message me and I can give better specifics.
@RubberDucky1106 what you have so far seems to be exactly what we want the api to do for us as well. The manual process of downloading the various scan reports through the UI is currently very time consuming. In reviewing the script "Get-AcunetixReport.ps1" the line where you have the following: "$reports = $webclient.DownloadString("https://$($server):3443/api/v1/reports") | ConvertFrom-Json"
Would you recommend just defining the server variable like you would any other variable? API key is pretty straightforward, thinking we would do something similar to that. Just wanted to make sure there wasn't some sort of login or ideas that we might be missing.
Thanks!
@RubberDucky1106 this doesn't seem like a real issue as it is more a question. We are just getting started with working on using Powershell in conjunction with Acunetix. What you have coded looks great, hoping to maybe work with what you have so far and building off of it. With the functions that you are calling, is there a calling script or some sort of configuration file that you are using for the various functions to reference?