fix(microsoft-entra-id): Support corporate proxies with customFetch
#12810
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☕️ Reasoning
The library supports corporate proxies using a custom fetch function with the customFetch property. However, the MicrosoftEntraID provider cannot be used from behind a corporate proxy because the built-in
fetch
function is used unconditionally within the provider instead. ThecustomFetch
function should always be used in place of the built-infetch
when it is defined.This pull request patches the
MicrosoftEntraID
provider always to use thecustomFetch
function if it is defined, allowing it to be used from behind corporate proxies.🧢 Checklist
🎫 Related issues
Relates: #12291
📌 Resources
🩹 Other possibly affected providers
The built-in
fetch
function is also used in many other providers. Based on its usage, the following providers could be affected by the same issue. I have not tested the hypothesis.