Calling APIs with SharePoint Framework
Download as PPTX, PDF0 likes316 views
The document discusses connecting SPFx with secured APIs, focusing on calling third-party APIs, SharePoint REST APIs, and Graph APIs. It highlights the need for tenant administration permissions to access these APIs and outlines considerations for architecture, including API security through Azure AD app registration. Additionally, it introduces isolated web parts and their configuration within the application package.
Calling APIs with SharePoint Framework
- 1. CONNECT SPFX WITH SECURED APIS GIUSEPPE MARCHI â DEV4SIDE WWW.PEPPEDOTNET.IT - WWW.DEV4SIDE.COM
- 2. HELLO, I AM PEPPE ďĄ Founder of Dev4Side S.r.l. ďĄ Microsoft MVP for 10 years in a row ďĄ Speaker on community of official Microsoft events in Italy ďĄ "SharePointer" from 2005 ďĄ Father of www.peppedotnet.it ď ďĄ Office 365 advisor for www.office365italia.com ďĄ Author of the book "Pocket C#â - Apogeo ďĄ One of the SharePoint and Office 365 influencers (for 2014 e 2015)
- 3. AGENDA ďĄ CALLING THIRD PARTY APIS ďĄ CALLING SHAREPOINT REST APIS ďĄ CALLING GRAPH APIS ďĄ CALLING ENTERPRISE APIS ďĄ ISOLETED WEB PARTS
- 4. DEMO HOW TO CALL THIRD PARTY APIS (ANONYMOUS) AND SHAREPOINT REST APIS
- 6. CALLING ENTERPRISE APIS - CONSIDERATIONS You will need to have tenant administration permission to grant access to Graph APIs Granted permissions for the Graph API apply to all customizations running in the tenant
- 7. CALLING ENTERPRISE APIS CONSIDERATIONS AND ARCHITECTURE
- 8. CALLING ENTERPRISE APIS - CONSIDERATIONS Even though API is hosted in the same Azure AD, thereâs no access to it by default You will need to have tenant administration permission to grant access to APIs Granted permissions for the API apply to all customizations running in the tenant If you are hosting the API in a different Azure AD, you need admin consent (multi-tenant)
- 9. ARCHITECTURE
- 10. CALLING ENTERPRISE APIS â HOW TO ďĄ Secure the API with a new Azure AD app registration ďĄ Enable CORS ďĄ Insert the needed permission inside package-solution.json ďĄ Build and deploy the solution in the app catalog ďĄ Approve the requested permissions from SharePoint Administration portal ďĄ âŚ now you can start debugging!
- 11. DEMO HOW TO CALL ENTERPRISE APIS
- 12. ISOLATED WEB PARTS WHAT ARE THESE?
- 13. ISOLETED WEB PARTS Even though API is hosted in the same Azure AD, thereâs no access to it by default You will need to have tenant administration permission to grant access to APIs Granted permissions for the API apply to all customizations running in the tenant If you are hosting the API in a different Azure AD, you need admin consent (multi-tenant)
- 14. ISOLETED WEB PARTS - ARCHITECTURE
- 15. ISOLATED WEB PARTS ďĄ The choice to have an isolated web part can be done during new project generation or anytime modifying the property "isDomainIsolated" available inside package-solution.json file ďĄ So is the entire package that is "domain isolated" ! ďĄ Isolated web parts run inside an iframe ďĄ Pay attention at UI and UX! ďĄ A specific App Registration is automatically created inside your Azure AD once permissions are approved ďĄ If you need to revert back an isolated web part, remember to first remove the package from the App Catalog
- 16. GRAZIE ď GIUSEPPE MARCHI â DEV4SIDE