Skip to content
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

SecurityInsights: ThreatIntelligence (TAXII) Data Connector API not round trip consistent #21487

Closed
magodo opened this issue Nov 9, 2022 · 3 comments
Labels
SecurityInsights Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@magodo
Copy link
Contributor

magodo commented Nov 9, 2022

The taxiiLookbackPeriod is defined as a "date-time" format in Swagger, which represents a RFC3339 date time. Whilst, on return it is in format "01/02/2006 15:04:05".

The pollingFrequency is defined as an enum. When specifying it using one of the enum value (a string), it returns an integer (0, 1, 2) in response.

The issue exists for both TI and TI TAXII data connector resources, at least for 2022-10-01-preview.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 9, 2022
@JackTn JackTn added Service Attention Workflow: This issue is responsible by Azure service team. SecurityInsights labels Nov 10, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 10, 2022
@ghost
Copy link

ghost commented Nov 10, 2022

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amirkeren.

Issue Details

The taxiiLookbackPeriod is defined as a "date-time" format in Swagger, which represents a RFC3339 date time. Whilst, on return it is in format "01/02/2006 15:04:05".

The pollingFrequency is defined as an enum. When specifying it using one of the enum value (a string), it returns an integer (0, 1, 2) in response.

The issue exists for both TI and TI TAXII data connector resources, at least for 2022-10-01-preview.

Author: magodo
Assignees: -
Labels:

Service Attention, needs-triage, SecurityInsights

Milestone: -

@pho-enix
Copy link

This is killing the python SDK:

Unable to deserialize response data. Data: 01/01/1970 00:00:00, iso-8601

Thus I would like to encourage you to go for ISO-8601 instead of RFC3339, as ISO-8601 is a subset of RFC3339.

@magodo
Copy link
Contributor Author

magodo commented Jun 13, 2024

Service has fixed this API, closing it.

@magodo magodo closed this as completed Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SecurityInsights Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants