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.

Sign up for GitHub

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

Jump to bottom

Mandiant connector using the incorrect endpoint for reports #704

Closed
RaulSokolova opened this issue Jun 6, 2022 · 0 comments
Closed

Mandiant connector using the incorrect endpoint for reports #704

RaulSokolova opened this issue Jun 6, 2022 · 0 comments
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 5.3.3

Comments

@RaulSokolova
Copy link
Contributor

Description

Latest Mandiant connector 5.3.2 is not pulling reports and getting permission denies when trying to pull reports due the wrong url path or typo.

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. replace url = self.mandiant_api_url + "/v4/report" with url = self.mandiant_api_url + "/v4/reports"

Logs

DEBUG:urllib3.connectionpool:https://api.intelligence.fireeye.com:443 "GET /v4/report?limit=1000&start_epoch=0&end_epoch=3600 HTTP/1.1" 403 11
ERROR:root:Query failed, permission denied
SamuelHassine added a commit that referenced this issue Jun 6, 2022
@SamuelHassine
[mandiant] Fix reports URL (#704)
5fb4d2a
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Jun 6, 2022
@SamuelHassine SamuelHassine added this to the Release 5.3.3 milestone Jun 6, 2022
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 5.3.3
Development

No branches or pull requests
2 participants
@SamuelHassine @RaulSokolova