Actions21
- Project Actions
- Application Actions
- Test Actions
- Domain Verification Actions
Test → Stop
AI-generatedOverview
This node interacts with the Beagle Security API to manage and control security tests for applications. Specifically, the 'Stop' operation under the 'Test' resource allows users to stop a running security test by providing the application token and the result token of the test. This is useful in scenarios where a test needs to be halted before completion, such as when an issue is detected or the test is no longer needed.
Use Case Examples
- Stopping a running security test on a web application by providing the application token and the result token obtained when the test was started.
- Halting a security scan to conserve resources or to adjust test parameters before restarting.
Properties
| Name | Meaning |
|---|---|
| Application Token | The unique token identifying the application on which the test is running. Required to specify which application's test to stop. |
| Result Token | The token representing the specific test result instance that is currently running and needs to be stopped. |
Output
JSON
json- The JSON response from the Beagle Security API after attempting to stop the test, containing details about the stopped test or any error messages.
Dependencies
- Beagle Security API
Troubleshooting
- Ensure that both 'Application Token' and 'Result Token' are provided and valid; missing or incorrect tokens will cause the API request to fail.
- If the test is already stopped or the tokens do not correspond to a running test, the API may return an error or no action will be taken.
- Check API authentication token validity as expired or incorrect credentials will result in authorization errors.
Links
- Beagle Security API Documentation - Official API documentation for understanding endpoints and parameters used by the node.