Skip to content

Show configured DAST profile details on DAST Security Configuration

Artur Fedorov requested to merge 365226-show-configured-dast-profiles into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Based on completed backend task #90713

This MR resolves frontend part of #365226 (closed)

Now after refreshing the page, user can still see saved on backend profiles

dast_profiles_configurator is used several places (on_demand_dast scans and dast configuration)

Saved profiles can be passed either via savedProfiles or via savedScannerProfileName and savedSiteProfileName

savedProfiles are used for on_demand_scans as objects come already with ids from backend

for dast configuration, we receive only profile names.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

after
saved_profiles

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Select project with DAST configuration disabled
  2. Go to URL/root/PROJECT_ID/-/security/configuration/dast
  3. Open sidebar and create at least 2 scanner and 2 site profiles (only one will be selected by default)
  4. select scanner profile and site profile
  5. Copy code snippet and commit changes to .gitlab.yml
  6. Go back to URL/root/PROJECT_ID/-/security/configuration/dast
  7. Profiles should be saved even after refresh and have in-use label

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #365226 (closed)

Merge request reports