Unrecognised active scan policy name for job activeScan

68 views
Skip to first unread message

Jernej Rus

unread,
Nov 27, 2025, 10:16:39 AMNov 27
to ZAP User Group
I have a ZAP YAML file with multiple jobs, including activeScan-policy and activeScan. activeScan-policy defines a policy named testPolicy and activeScan uses it. Trying to run the plan fails with error:

25890 [main] ERROR org.parosproxy.paros.CommandLine - Unrecognised active scan policy name for job activeScan : testPolicy

Running -autocheck fails with the same error.

I'm running this in an image where the add-ons have the latest versions. I did not get this error in an older image. I also see that you added validation of the Scan Policy in 0.54.0. Perhaps it broke something? Is this a valid error or a bug?



kingthorin+zap

unread,
Nov 28, 2025, 9:35:15 AMNov 28
to ZAP User Group
Could you provide the actual yaml, with creds/URLs redacted

Jernej Rus

unread,
Nov 28, 2025, 10:13:11 AMNov 28
to ZAP User Group
Here is a version of my YAML file with some env masked and some jobs removed. It still produces the error.
plan.yaml

Austin Bruch

unread,
Dec 1, 2025, 9:52:46 AMDec 1
to ZAP User Group
I am seeing a similar error. I have a ZAP scan set to run once a week, pulling the docker image `zaproxy/zap-stable`, and this seemed to start happening somewhere between 2025-11-04 and 2025-11-11, with no changes to the ZAP YAML file on my end. Possibly a change introduced in the stable image that was released within that time range?

thc202

unread,
Dec 1, 2025, 10:00:05 AMDec 1
to zaprox...@googlegroups.com

Jernej Rus

unread,
Dec 9, 2025, 3:13:24 AM (11 days ago) Dec 9
to ZAP User Group
Hello. Have you discovered anything?

Jernej Rus

unread,
Dec 10, 2025, 4:51:37 AM (10 days ago) Dec 10
to ZAP User Group
:) I see that you have made https://github.com/zaproxy/zap-extensions/pull/6954. Indeed, ZAP no longer fails when running my YAML file.

Simon Bennetts

unread,
Dec 15, 2025, 11:46:03 AM (5 days ago) Dec 15
to ZAP User Group
Yes, thank you for reporting that issue, and it has now been fixed :D
Reply all
Reply to author
Forward
0 new messages