-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOC IndicatorCreateV1 issue with Body #426
Comments
Update: It looks like using the REST API via cURL/Postman, you don't need to specify the expiration field but with the SDK it's required otherwise it defaults to a 0 value strfmt.Time which results in an expiration needs to be in the future error (the SDK for some reason wasn't including this in the response, I used the API directly with go code and read the response to get this error out) |
hey @ks2211 can you check if |
@ffalor thanks! that seems to have fixed it for me. will wait for the v0.7.0 tag to be pushed |
hey @ffalor I'm dealing with a slightly strange issue now -- I used the 0.7.0-rc1 on my local machine and everything seems to work with creating indicators. Any ideas what could cause that issue? EDIT: turns out it was a timezone issue and parsing on my remote servers, going to close this |
Using version v0.6.0 with go version 1.22.1
I am attempting to create an IOC using the ioc.Client.IndicatorCreateV1 method but getting a 400
One or more indicators have a warning or invalid input
errorThis is the request body I use via cURL/Postman and I get a succesful 200 response (along with the id).
This is the equivalent go code but results in a 400 error.
indicatorCreateV1BadRequest &{Errors:[{Code:400 Message:One or more indicators have a warning or invalid input}] Meta:PoweredBy:ioc-manager QueryTime:0.012351665 TraceID:<TRACE>}}
Checking the generated source vs the json above, everything seems to match up(with the only exception being the bool pointer for the applied_globally field but marshalling usually handles that). It doesnt seem to fail validations either and makes it to the API which then returns the error and I can't see any differences between go vs the curl json blob.
Any suggestions?
The text was updated successfully, but these errors were encountered: