Please add the option to integrate a connector into a Harness native DAST step
C
Casual Dove
Hi,
I am trying to use DAST scanning in my pipelines, and due to limitations on session tags, I am unable to connect to my target AWS account instances from the delegates sitting in another AWS account.
Currently our configuration uses AWS Connectors to support connectivity between both accounts for all other operations, and this allows us to use OIDC connectivity to enforce which pipelines are accessing AWS resources. This is done through OIDC session tags.
If we are to go with the current configuration in DAST with direct IP connectivity, the additional configuration and security approvals needed could take up to a month.
Please let me know if this is an option.