馃帹 Design: DAST Site profile: Header addition redesign
Problem
The current Additional Headers textarea makes it difficult to provide security for headers that are sensitive and should be masked when viewing the config summary or editing a profile, while at the same time allowing users to see the values for headers that are not sensitive. Since it is a single textarea form field, it is an all or nothing approach to masking the headers.
Proposal
Instead of using a textarea, we should allow each header to be defined as a row that has a Header field, a Value field, and a Protected/Masked/Sensitive checkbox. There should be an "Add additional header" button below the form area to add another row to the table of headers. There should also be a way to delete a row after it has been added to the table.
Once the profile is saved, any header marked with the 'Protected' checkbox should be encrypted and masked from ever showing up in the config summary or when editing the profile. This attribute should not be allowed to be changed once the profile is saved.