How this template works
APIs Selection
The API selection filters in this template specify the criteria for selecting the API to be tested. In this case, the filters include checking the response code to be greater than or equal to 200 and less than 300, and extracting the URL from the response to be used in the subsequent request.
Execute request
The execute section defines the type of request to be executed, which is a single request in this case. It also specifies the request to be made by modifying the URL variable extracted from the previous response. The modified URL is appended with "/actuator/beans" to access the Spring Boot Beans Actuator endpoint.
Validation
The validation section defines the expected response code and payload to validate the success of the request. In this template, the response code is expected to be 200, indicating a successful request. The response payload is checked to contain specific attributes such as "type", "beans", "dependencies", and "scope" to ensure that the Actuator endpoint is providing the expected information.
Frequently asked questions
"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "
Security team,
Rippling
Explore other tests
eSMTP - Config Discovery
Nginx - Git Configuration Exposure
Laravel - Sensitive Information Disclosure
Docker Container - Misconfiguration Exposure
Msmtp - Config Exposure
Parameters.yml - File Discovery
Mongo Express - Unauthenticated Access
Apache Airflow Configuration Exposure
Dockerrun AWS Configuration Exposure
Apache Config file disclosure
Appspec Yml Disclosure
CGI script environment variable
