DAST authentication should support a secondary username field
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
A common authentication sequence for Multi-tenant SaaS systems to to have an organization, or secondard user ID field. DAST auth should support this.
Proposal
Add a secondary username field to the configuration options DAST_USERNAME2 and DAST_USERNAME2_FIELD (or come up with better variable names).
Intended users
What does success look like, and how can we measure that?
DAST is able to authenticate to systems that have multiple username input fields.
What is the type of buyer?
Links / references
Edited by 🤖 GitLab Bot 🤖