ESET PRIVATE Scanning Solution – Table of Contents

Authentication error

Copy current article URL Share via email

This article (PDF) Whole documentation (PDF)

When the scanner agent is run with invalid credentials, it cannot authenticate with the scanning service and is unable to start the scan. In this situation, the agent returns an authentication failure—typically resulting in an HTTP 401 error, which means "Unauthorized." Because the connection cannot be established, the scan does not proceed.

Command:

scanner_agent -t 'example.com/load_balancer:50052' -s -a
https://example.com/scanner/protocol/openid-connect/token -u 'bad_username' -p
'bad_password' -v a7d4e2e63bef19fffee19920e82211f88e5e72cca19b7278f05a88499665e35a
--skip_cloud_reputation /bin/bash

Default Scanner JSON response example:

Will scan these files:
/bin/bash
HTTP POST request failed with status code 401
Failed to create channel

Explanation of JSON Fields and the result:

•If the username or password is incorrect, authentication will fail, and no scan will be performed.

•The output specifically shows "HTTP POST request failed with status code 401," signaling that the request was not authorized.

•"Failed to create channel" means the scanner could not establish a secure session with the scanning service due to the failed login attempt.

•Always verify that the correct credentials and server configuration are provided when this error occurs, as the scan cannot proceed until valid authentication details are supplied.

˄˅