Disable policy DAST scan profile modification
What does this MR do?
Disable policy DAST scan profile modification
- if a policy is linked to a DAST scan/site profile, do not allow a user to modify it on the On-demand scan page
How to test
https://gitlab.com/-/snippets/2088929
Screenshots (strongly suggested)
I am only showing the disabled screenshots because otherwise the pages look the same
Page | Screenshot |
---|---|
Site List - Large | ![]() |
Site List - Small | ![]() |
Scanner List - Large | ![]() |
Scanner List - Small | ![]() |
Site Profile - Disabled | ![]() |
Site Profile Auth - Disabled | ![]() |
Scanner Profile - Disabled | ![]() |
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #321886 (closed)
Edited by Alexander Turinske