Closed smahoney58 closed 7 years ago
This error was found on Newman v2.1.1
Kevin did find a workaround where he enters something like the following directly into the browser bar: http://localhost:9200/newman-shiavo/emails/28411a44-22f6-11e6-afc5-080027542fa4
This doesn’t show the content, but gives all the metadata from the Elasticsearch index which is what he was trying to get to.
The latest v2.1.1 Newman does not have an ID field anymore; now includes an Email ID and Case ID. Need to discuss this issue with Kevin English and potentially Charles Ramsay. The Email ID and Case ID request came from ? ( I believe it was the FBI via Charles Ramsay but maybe it was from some other source). Current implementation does not meet the goals that Charles/Kevin were looking for.
In Newman v2.1.3 Email ID is correctly populated with a GUID. It is no longer a link. Will let Kevin and/or Charles create a more detailed issue if this is not the behavior they desire. Kevin can still use his workaround. I'm guessing most analysts don't need the ElasticSearch metadata.
When you try to follow the link for ID (located in left-panel email view), you get an error message in the main browser window.
Steps to Reproduce
Results: A tab created with the following error information. <!doctype html>
501 Error in Python Service
There was an error executing service /email/0732a020-22f6-11e6-afc5-080027542fa4/0732a020-22f6-11e6-afc5-080027542fa4.txt:
Powered by Tangelo
This error was found by Kevin English who needs to be able to follow the email ID to retrievethe metadata for the email.