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.

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

Question: JWT scope limited in some tenants #109

Open
ChoboSyk opened this issue Jan 9, 2025 · 0 comments
Open

Question: JWT scope limited in some tenants #109

ChoboSyk opened this issue Jan 9, 2025 · 0 comments

Comments

@ChoboSyk
Copy link

ChoboSyk commented Jan 9, 2025

Hi,

In some tenants where I'm testing, when I obtain a JWT using the authorization code flow the default set of permissions/scope will be different even when using the same Client and Resource combination.

Example:

  • Client ID: Microsoft Teams (1fec8e78-bce4-4aaf-ab1b-5451cc387264)
  • Resource: api.staffhub.office.com (aa580612-c342-4ace-9055-8edee43ccb89)

In some tenants I will obtain the whole set of permissions/scope defined in firstpartyscopes.json but in others they will be limited to only a few or none. I will get a JWT back nonetheless but it will be mostly useless as API calls will return 403 as the scope is limited.

I've been trying to figure out what mechanism is used to limit the scopes returned to an external app such as Microsoft Teams when accessing a specific resource but I can't figure it out.

Apologies if this isn't the right place to ask.

Any insight would be greatly appreciated.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant