[Bug] Autofocus Analyzer Error - "Image not found"

[packetvitality]

Request Type

Bug / Analyzer

Work Environment

Cortex-Analyzers 2.4.0

Question	Answer
OS version (server)	Ubuntu
OS version (client)	Windows
Cortex Analyzer Name	AUTOFOCUS_SearchIOC_1_0
Cortex Analyzer Version	1.0
Cortex Version	Cortex-Analyzers 2.4.0
Browser type & version	N/A

Description

When attempting to use the analyzer, the following error is returned:
"errorMessage": "Image not found: cortexneurons/autofocus_searchioc:1",

Steps to Reproduce

1.) Add IOC (tested IP and domain)
2.) Run analyzer.

Complementary information

Using Dockerized analyzers. Upgraded by using the "Refresh analyzers" option within Cortex.

[jeromeleonard]

we currently experience issues with our container repository... we are working on this.

[jeromeleonard]

a hot fix 2.4.1 has been published. please update your analyzers ans you should be able to get the docker image. Please confirm everything is working before closing the issue.

[packetvitality]

Thank you.

I refreshed and tried to rerun. Now getting an error for the API key. Note in the full error below, I did not put "REMOVED" for the apikey, that is just what the error shows. In previous runs, the error actually showed my API key there. I'd agree it is better that it is removed if that is intentional, just wanted to note the difference.

I double checked the Cortex configs to make sure my key was in there, also deleted and re-enabled the configs.

{
"input": "{"data":"103.208.220.122","dataType":"ip","tlp":2,"message":"8","parameters":{},"config":{"proxy_https":null,"cacerts":null,"max_pap":2,"apikey":"REMOVED","jobTimeout":30,"service":"search_ioc","check_tlp":true,"proxy_http":null,"max_tlp":2,"auto_extract_artifacts":false,"jobCache":10,"check_pap":true},"pap":2}",
"success": false,
"errorMessage": "Unexpected Error: (ClientError(...), 'API key is not set. Library requires AutoFocusAPI.api_key to be set, or apikeyto be provided via configuration file.')",
"artifacts": []
}

[jeromeleonard]

@packetvitality unfortunately there is a problem with the library ( see #473 (comment))