-
### Enhancement Request
Issue #452 had the original fod `dast-scan start` and `dast-scan get-config` commands hidden and renamed with a `-legacy` prefix in order to accomidate the new FoD DAST Automa…
-
- Decide where in the command tree these commands should be located
- Implement these commands
-
With fcli SSC's `list` commands, if you try to limit the number of results being output by using the RESP APIs `limit` parameter, it won't work for two reasons:
- If any `-q` options are specified…
-
👋 Hello! Not sure if this is the right place to raise this issue, but we've noticed that the way Fortify SCA is generating SARIF documents is causing a bad user experience with GitHub Code Scanning.
…
-
We are testing fastnetmon.
fcli show total_traffic_counters
incoming traffic 50413 pps
incoming traffic 269 mbps
incoming traffic 17 flows
outgoing traffic 7160 pps
outgoing traffic …
-
### Current Behavior
The DAST Automated API does not handle queiring of scan requests, so if a DAST scan is requested whilst one is running, the following error is produced:
```
Run fcli fod dast…
-
### Current Behavior
**Issue**
We are encountering intermittent 404 errors while making API calls in FCLI to poll for Fortify scan results. Here is a concise overview of our scan process.
- Aut…
-
The `-o tree` option outputs data in tree format using the original JSON property names. Since this is supposed to be a human-readable format, we should probably output formatted and possibly internat…
-
### Current Behavior
I am curently using fcli version 2.6.0 (and I see that 2.7.1 is out). When I den do a
`fcli tool sc-client install `
Then I get a stack trace like:
```
java.lang.Illegal…
-
We're trying to have our application properly handle paths starting with `~` to represent the user home directory. It seems like `bash` is already taking care of expanding `~` references with the prop…