Uploading an Archive
If an archive with that name already exists, the following error message displays this message: The file with that name already exists or the HAR file is corrupted
.
Important
If you plan to run a scan using an OAS file, you must specify a different discovery option by setting the
--discovery
to OAS.
Arguments
Argument | Description |
---|---|
<file> | A collection of your app logs exported into a .HAR file. Typically, you can use any browser's dev tools, or a Cypress plugin to generate them. In addition, you can use an OAS file that describes your public API. |
Options
Option | Description |
---|---|
| The unique identifier used to authenticate a user. The token (API key) can be issued in your organization’s dashboard. |
| The specification type, which helps determine the best way to parse passed files.
|
| When true, removes an archive from the cloud storage after the scan finishes running.
|
| Extra headers to be passed with the OAS/Postman file. Also, it can be used to remove a header by providing a name without content. For example,
|
| Environment variables passed with the Postman file. |
| Specifies the path to the configuration file. By default, the CLI tries to discover the config in the |
| Allows setting the level of logs to report. Any logs of a higher level than the one specified are shown. The options to select : 0, 1, 2, 3, 4, "silent", "error", "warn", "notice", and "verbose".
|
| Bright cluster (domain name).
|
| Allows the Bright CLI to proceed and operate even if the server connection is considered insecure. |
| SOCKS URL to proxy all traffic.
|
|
|
Updated 16 days ago