HTTPClassyProbe spams Discovery log with Warnings after Newyork upgrade: No credential found for type [BASIC_AUTH] - Known Error

HTTPClassyProbe spams Discovery log with Warnings after Newyork upgrade: No credential found for type [BASIC_AUTH] Description Discovery log warnings after Newyork upgrade from HTTP Classify Probe: No credential found for type [BASIC_AUTH].

The Discovery log can be heavily spammed by this log, making identification of real issues difficult. The F5 Classifier causes it, which may not need to be used by all customers. This warning is given if there is no Basic Auth credential entered in the Credentials table yet, and the customer may not want or need one.

Steps to Reproduce

Install Discovery and a MID Server Do NOT add any Basic Auth type credentials Run Discovery against anything that may have port 80 or 443 open.

An HTTP Classifier is included for F5. This will run against the IP if the ports are open. For each IP, this Warning will appear in the Discovery Log:

"No credential found for type [BASIC_AUTH]" for HTTP Classify HTTPClassyProbe

Workaround This is expected behavior and by design in all currently supported releases.

These warnings can be ignored, because all they are really saying is that you can't expect the http classifiers to do anything.

Adding a dummy basic credential won't help you, as this will replace all these warnings with other warnings about there being no valid credential instead.

If you know you don't need some of the out-of-box HTTP Classifiers, some can be deactivated, and that will reduce the number of warnings. e.g. if you have no F5 load balancers, you may choose to deactivate the "F5 HTTP" classifier.