TAXII service not submitting

[ghost]

I'm attempting to setup a taxii connection using the updated taxii service, however when I hit "submit" the feed is not actually saved into the service configurations. Any help?

[brlogan]

Strange. Did you figure this out? When you click the "Submit" button on the feed form, it should immediately save that data to the config unless it encounters an error. For example, if the provided CRITs Source doesn't exist in CRITs, an error should be displayed and the feed form shouldn't be hidden.

When you click "Submit" on the feed form, does it hide the feed form and show the server config form again? Do the server config details get saved, just not the feeds? Any other details you can provide on the behavior?

[ghost]

I have not figured this out yet. When I click the submit button, it remains on the feed form and doesn't return to the server config form. I also don't get any errors when clicking submit, it just remains on the form.

[mgoffin]

And you've opened up Developer Tools and looked at the request being made and the response you get?

[ghost]

I am getting an Internal Server Error when attempting to POST. Above is the info I am using for my feed config.

[brlogan]

I'm guessing there is something wrong in the DB with your service configuration. If you can provide the response body for the POST, or the contents of the taxii_service document in the "services" collection of your DB, then I can probably find the issue.

[ghost]

{ "_id" : ObjectId("575acdcc1d41c86ca49864c4"), "schema_version" : 1, "name" : "taxii_service", "config" : { "ns_prefix" : "test", "max_rels" : 200, "namespace" : "http://www.testinstance.com", "create_events" : false, "taxii_servers" : "" }, "compatability_mode" : false, "description" : "Send TAXII messages to a TAXII server.", "status" : "available", "supported_types" : [ ], "version" : "2.1.0", "enabled" : true, "run_on_triage" : true }

[ghost]

TaxiiServiceResponseBody.txt

Here is the entire response body from the HTTP POST

[brlogan]

Very helpful! I found the problem. Sure enough, part of your service configuration is in an unexpected format. I'll try to figure out how that might have happened and provide a fix.

Did you have an old version of the taxi_service installed previously, or did you just add the current version to your CRITs instance?

[ghost]

Thanks for looking into this! I essentially just installed a clean version of CRITs and just used the current version in my CRITs instance. All coming from the master branches.

[brlogan]

Okay, I think I have this fixed. Grab the update in #232 and let me know if it works for you.

[ghost]

This worked! thank you brlogan, much appreciated

[brlogan]

Great! You are welcome, @grwerbacher! Sounds like this issue can be closed.