Creating Cloud-Ready Enterprise Applications with the SharePoint 2013 Add-In Model.pptx
Download as PPTX, PDF1 like728 views
This document discusses authorization methods in SharePoint including OAuth and access tokens. It also summarizes differences between .NET and JavaScript for developing SharePoint solutions. REST APIs are covered as well as options for deploying SharePoint apps such as the App Catalog, Office Store, and private packages. Trust models like high trust using certificates and low trust with Azure ACS are also summarized.
Creating Cloud-Ready Enterprise Applications with the SharePoint 2013 Add-In Model.pptx
- 2. @eshupps sharepointcowboywww.sharepointcowboy.com slideshare.net/eshupps linkedin.com/in/eshupps Eric Shupps SharePoint Server MVP
- 7. SharePoint 2013 Sites ServicesContent API Oauth App Package HTML/JS Data
- 11. User requests access App requests Request Token Provider returns Request Token App builds auth link w/ Request Token User requests URL + Request Token Provider returns access token User requests URL + Access Token App validates access token Access token validated User granted access 1 2 3
- 20. REST O365 Only Delve Users FilesGroups Mail ContactsCalendar
- 23. Web Parts App Parts Application Pages Web Pages Timer Jobs Web Jobs List Templates Code Web Templates Provisioning Event Receivers Remote Event Receivers
- 26. App Catalog Office Store Private Package Validation No Licensing Public App Validation Licensing Framework
- 27. High Trust Certificates Token Issuers Client ID’s and Secrets Low Trust Azure ACS Hybrid Tokens
- 28. Single Sign On User & Group Assignment App Permissions App Launcher Azure Portal
Editor's Notes
- #10: OAuth is an open standard for authorization. OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections. Grew out of collaboration between Twitter, Google, and other social computing vendors, as a means to provide user access and API integration, primarily via OpenID, without requiring individual accounts.
- #14: S2S_Server S2S_App_HighTrust
- #17: S2S_Server S2S_App_HighTrust
- #19: S2S_Server S2S_App_HighTrust
- #22: S2S_Server S2S_App_HighTrust
- #23: S2S_Server S2S_App_HighTrust
- #26: S2S_Server S2S_App_HighTrust