-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
[BUG] Missing Auth when downloading Blob URL #72
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the Client tries to download the Blob file from Microsoft, it seems not to send the Bearer Token with the Request:
Whatever I try, I get these error message:
[00:00:05.458] (42c) ERROR Err getting blob response error sending request for url (https://manage.office.com/api/v1.0/xxxxxx/activity/feed/subscriptions/content?contentType=Audit.AzureActiveDirectory&startTime=2024-06-19T08:01:55Z&endTime=2024-06-20T08:01:55Z&PublisherIdentifier=12345678-1234-1234-1234-123456789123): operation timed out
Connections and Permissions seems to look good. The Collector also Downloads a bunch of Content. But when the Collector tries to download the Blob, it fails.
Log from the Console
Logging is also enabled:
![image](https://private-user-images.githubusercontent.com/25774289/341328829-dd94cb15-be52-4f49-83c4-31794b46fe3d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA4NTU2NDEsIm5iZiI6MTcyMDg1NTM0MSwicGF0aCI6Ii8yNTc3NDI4OS8zNDEzMjg4MjktZGQ5NGNiMTUtYmU1Mi00ZjQ5LTgzYzQtMzE3OTRiNDZmZTNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzEzVDA3MjIyMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMxZGVkYmJjNWY3ZWQ0ZTRlYjIzMjRlZjFjZTQxMDlkMjk1ZjVlZjAxMDMwZmY0OTg2YjU1ZjliMTQxYzhjNTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.FNBnvUaX1GxPDU-RgB0OhwVlL3pRW-NIWvrSyHCHNko)
The text was updated successfully, but these errors were encountered: