-
Notifications
You must be signed in to change notification settings - Fork 304
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] v3 401 errors when using a custom api uri scope #2589
Comments
Hello nickjisc, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
Recommend exposing the ability to set customHosts on the underlying graph client on init |
Hi @nickjisc, thanks for raising this and also for the recommendation on exposing the ability to set customHosts on the graph client. We will look into this and provide an update as soon as possible. We also really love community fixes, would you like to submit a PR for this? |
I'll try and have a look, the PR will come from my personal account if I manage to do expose that config |
Hopefully I've done #2592 right |
Describe the bug
Updated from v2 to v3 and calls to AAD secured endpoints produces a 401 error with both and Providers.client.get("uri").
then
The above call produces a 401 error on v3 but v2 works fine. Same behaviour when using
To Reproduce
Steps to reproduce the behavior:
If you add the api scope after the graph scopes, it fails to get that scope but graph scopes will work
Expected behavior
To continue to function as v2
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: