Write-Error contains bearer access token and is written in the console log

[milapointe]

Using EntraExporter and not having sufficient rights, it give an error. This error is not handled by the module and passed through the console log and we can clearly see the bearer access token (stripped from this capture)

Any way to hive this part of the request? I don't mind having the error but having the access token all over in the logs....even if it's valid only for 1 hour and having limited access, I prefer not having it :)

Thanks !

[ptmetcalf]

The skiptoken field wouldn't be an access token, it's just used for pagination in the Graph API to handle large datasets. If you wanted to redact that or something from the output you could always wrap the command in a try/catch and use regex to redact any output that you don't want to see.

[milapointe]

See below, I mask the authorization header bearer... its weird on dark mode browser 😅

Plus, I run this inside an azure function so maybe its more verbose than usually.

[SamErde]

I'm going to add this to my next-up list. @milapointe, do you have a good way to reproduce this for testing?

[SamErde]

Just to be clear, I don't own this repo or have the ability to merge changes but I know how to bug a guy that can. 😉 Let's keep contributing to improve and enhance a great community tool.

[milapointe]

Hi, I was doing a full export into an azure function. A simple powershell script that import the module EntraExporter. Keep in mind you have to put greater timeout for the azure function so that it wont fail.

the initial problem I was working on was this : #62

[SamErde]

Do you have any time to test my solution in #74?