Skip to content

Document issues / limitations of DAST Site Profiles Auth Options

This is to document all known issues / limitations of DAST Profile's authentication options built in &3771 (closed)

  1. Non-blocker: Avoid sending additional payloads (auth options) when authentication is disabled severity4

    Exampleimage

  2. Non-blocker: Show better error descriptions severity3

  • When min length requirement is not met for request headers or password fields on saving a profile
    Exampleimage
  1. Empty out Request headers & Password fields
  • With the current implementation of storing / displaying the sensitive fields, it's not possible for user to empty out these values once set for a profile
  • One quick workaround is to create a duplicate profile
Edited by Dheeraj Joshi