search

SharePoint / sp-dev-docs

SharePoint & Viva Connections Developer Documentation
https://docs.microsoft.com/en-us/sharepoint/dev/
Creative Commons Attribution 4.0 International
1.24k stars 1k forks source link

API Access SharePoint Admin Page Issue #9915

Open sharepointalist opened 1 week ago

sharepointalist commented 1 week ago

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

Additional environment details

No response

Describe the bug / error

After installing a new version of SPFx package, API page reflects multiple instances of the same APIs (both in approved and pending). Approving API's essentially creates a copy. New package adds another copy to pending. On Entra side of things everything looks fine.

This issue happens on demo tenants, as well as customer tenants.

Screen Shot 2024-09-12 at 10 38 49 AM Screen Shot 2024-09-12 at 10 40 57 AM Screen Shot 2024-09-12 at 10 42 53 AM

Steps to reproduce

  1. Install SPFx package with Graph API's in webApiPermissionRequests
  2. Approve API's from SharePoint Admin Center
  3. Install new package
  4. Look into API access page again

Expected behavior

There should be only one instance of every Graph API on API access page.

sharepointalist commented 1 week ago

Just in case - looking into the oAuth2PermissionGrant response - it does return the following for the approved list - essentially showing scopes twice (as they are on a screenshot for approved). I did approve them twice, so it is kinda messed up now: "scope": "User.Read.All Files.Read.All Sites.ReadWrite.All Directory.Read.All Group.ReadWrite.All Organization.Read.All Sites.Manage.All InformationProtectionPolicy.Read TeamsAppInstallation.ReadForUser TeamsAppInstallation.ReadForUser InformationProtectionPolicy.Read Sites.Manage.All Organization.Read.All Group.ReadWrite.All Directory.Read.All Sites.ReadWrite.All Files.Read.All User.Read.All"

GrahamMcMynn commented 4 days ago

Thanks for reporting this issue. We have made a fix for this which should roll out around October the 2nd.