HawkScript fails with 'TypeError: Access to host class org.zaproxy.zap.authentication.AuthenticationHelper is not...

HawkScan's engine uses the com.stackhawk.hste package namespace. Rewrite the script's imports from org.zaproxy.zap to com.stackhawk.hste and rerun.

Context: Problem: A custom HawkScan authentication or business-logic script fails with an error like: TypeError: Access to host class org.zaproxy.zap.authentication.AuthenticationHelper is not allowed or does not exist. Cause: HawkScan's scan engine uses the com.stackhawk.hste package namespace, not the old ZAP namespaces. Fix: update the script imports: org.zaproxy.zap -> com.stackhawk.hste and com.stackhawk.zap -> com.stackhawk.hste. For example, org.zaproxy.zap.authentication.AuthenticationHelper becomes com.stackhawk.hste.authentication.AuthenticationHelper.

Matched source

Source: Source: https://docs.stackhawk.com/hawkscan/troubleshooting/ Original query: "HawkScript fails with 'TypeError: Access to host class org.zaproxy.zap.authentication.AuthenticationHelper is not..." Key terms: access, authentication, authenticationhelper, class, fails, hawkscript, host, typeerror, zaproxy

Source: Problem: A custom HawkScan authentication or business-logic script fails with an error like: TypeError: Access to host class org.zaproxy.zap.authentication.AuthenticationHelper is not allowed or does not exist. Cause: HawkScan's scan engine uses the com.stackhawk.hste package namespace, not the old ZAP namespaces. Fix: update the script imports: org.zaproxy.zap -> com.stackhawk.hste and com.stackhawk.zap -> com.stackhawk.hste. For example, org.zaproxy.zap.authentication.AuthenticationHelper becomes com.stackhawk.hste.authentication.AuthenticationHelper.

Verified resolution: HawkScan's engine uses the com.stackhawk.hste package namespace. Rewrite the script's imports from org.zaproxy.zap to com.stackhawk.hste and rerun.

Source URL: https://docs.stackhawk.com/hawkscan/troubleshooting/