You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating theHive server, Elastic-search, and then removing unused packages I broke Imap2thehive authentication into TheHive. During my troubleshooting I happened to stumble on using the API key for authentication instead of the Username Password combination and that seemed to resolve the bug.
Summary:
After updating theHive server, Elastic-search, and then removing unused packages I broke Imap2thehive authentication into TheHive. During my troubleshooting I happened to stumble on using the API key for authentication instead of the Username Password combination and that seemed to resolve the bug.
Error:
[ERROR]: Cannot create alert: 401 ({"type":"AuthenticationError","message":"Authentication failure"})
Testing Method
To test this solution I put the API key in the password field and reformatted TheHiveAPI call's configuration line.
OLD
api = TheHiveApi(config['thehiveURL'], config['thehiveUser'], config['thehivePassword'], {'http': '', 'https': ''})
Temporary Replacement
api = TheHiveApi(config['thehiveURL'], config['thehivePassword'])
Full Replacement process
I think this might be the full process to update the script. I am still working to figure out how the whole pull request system works.
[thehive]
section to addapikey:
field, then remove theuser:
andpassword:
fields.config['thehiveUser'], config['thehivePassword'], {'http': '', 'https': ''}
and addconfig['apikey']
The text was updated successfully, but these errors were encountered: