HTTP Classifier not working after Yokohama patch 7

[Curt4]

Hi everyone, we are using ServiceNow discovery and before Yokohama Patch 7 we could scan a Devices Webpage and the HTTP Classification Match would find the webpage and then it would kick off the correct pattern to run.

Now Discovery is trying to authenticate, I think, and since it doesn't need a username and password on the website, Discovery doesn't query the webpage and moves on.  If I go into Discovery Patterns and run the debug mode on the website of the device it works just fine, if I do setup an API Rest call to the device it comes back correct.  Just can't get Discovery Classifier to work.  I have a ticket open to SN, but not getting anywhere with it.  

• Here is the document on the change:
  Create an HTTP classification
  "Important: The HTTP Classify probe no longer attempts credentials over the HTTP protocol by default. To override this behavior, you can enable mid.http_classy.allow_credentials_over_http. However, enabling this setting can expose credentials to man-in-the-middle (MitM) attacks. Therefore, it’s strongly recommended to keep this property set to false and use HTTPS whenever possible."
• This is in the XML Payload from a scan:
  <result error="No credential found for type [BASIC_AUTH]" result_code="41">
  

[VijayaMannapura]

@Curt4  You check the old logs under tab 'Scan Log' and compare with the latest. Also, you can enable the property mentioned by SN in lower environments and try to 'Rescan'. 

[Curt4]

When this happened, it had been a week, so the old logs are gone.  I was thinking the same thing.
I put the property SN mentioned in the sys_property table and that didn't work, I also put it under the MID server Property table and that still didn't work.  
ServiceNow just got back to me and said the documentation doesn't seem to be accurate, so stay tuned to see what they find.  Thanks for ideas.

[Curt4 · Accepted solution]

We found the fix.  
1.  You need to add create this property (ecc_agent_property) in the MID Server property table (ecc_agent_property) not the sys_properties table.  
2.  Set it to Enabled.
3.  Then restart the mid server service or do a full reboot.  (I think when you restart the mid server, it pulls in any new configs.  This is what we were missing is restarting the mid server)