This document discusses developing hybrid SharePoint apps that can run both on-premise and in the cloud. It covers the new app model and authentication options for cloud, on-premise, and hybrid scenarios. The key aspects are using OAuth for cloud authentication, certificate-based trust for on-premise, and connecting on-premise farms to apps in the cloud for hybrid scenarios. Visual Studio 2013 tools simplify building single-codebase hybrid apps that work on-premise and in the cloud.
%+27788225528 love spells in new york Psychic Readings, Attraction spells,Bri...
Developing hybrid SharePoint apps that run on-premise and in the cloud - ESPC 2014
1. Developing hybrid SharePoint apps
that run on-premise and in the cloud
Bram de Jager
Macaw, The Netherlands
Microsoft Certified Solutions Master: SharePoint
2. Agenda
• Why do we need a new authentication model?
• Where does the new App model fit in?
• Inside OAuth
• Hybrid Apps
• Wrap-up
6. WHERE DOES THE (NEW) APP MODEL
FIT IN?
Developing hybrid SharePoint apps that run on-premise and in the cloud
7. Customization Options
Sandbox
Hosted in isolated
process
Limited server side
SharePoint API
access
No external
service calls
Full Trust
(a.k.a. Farm)
SharePoint
Apps
Server side
SharePoint API
access (SSOM)
Customizations to
file system or
servers
Hosted in same
process as
SharePoint
Classic model since
2007
New Apps model
Deployed from
corporate catalog
or Office Store
Runs outside of
SharePoint process
Can be deployed
on Azure, IIS,
Apache,…
Simple install and
upgrade process
Code sandboxed
solutions are
deprecated in
SharePoint 2013
8. Cloud, On-Premise, and Hybrid
• Cloud
– Azure AD (WAAD) in O365
– Apps use OAuth
• On-Premises
– Apps user cert based trust
– On-prem to on-prem
• Hybrid
– Combination of Azure AD
and on-prem SharePoint
Azure AD
Office 365App
App SharePoint
10. Scenario
• Build simple SharePoint-hosted app (list count)
• Deploy to on-premise App Catalog
• Deploy to online App Catalog
• Show lists in SharePoint Client Browser
11. Limitations SharePoint-hosted
• No custom server-side code (only HTML & JavaScript)
– Only supports current user in a page
– Can’t use elevated privileges
• No off-box logic
– Based on event in SharePoint
– No timer jobs available
23. Office Developer Tools support
• In Visual Studio 2012 the app checks availability of
the ContextToken (present or not)
– TokenHelper class, app helper class
• Visual Studio 2013 with the new release of Office
Developer Tools introduces a new class
– SharePointContext class, takes care of switching
between ACS or S2S trust
27. Summary
• The new App model is designed for both cloud and on-
premise
• Use the high-trust (S2S) authentication model for on-
premise scenarios
• In a hybrid environment connect on-premise SharePoint
farms to Apps in the cloud
• Build a single codebase hybrid App that works both on-
premise as in the cloud
28. Key takeaways
• Understanding authentication flow is a must for
every developer
• Don’t use Visual Studio 2012 any more
• Use Visual Studio 2013, make life a lot easier!
29. Resources
• Decode JWT, http://openidtest.uninett.no/jwt
• How to: Use an Office 365 SharePoint site to authorize
provider-hosted apps on an on-premises SharePoint site,
http://msdn.microsoft.com/en-
us/library/office/dn155905(v=office.15).aspx
– Microsoft Online Services Sign-In Assistant for IT Professionals
RTW (64-bit), http://www.microsoft.com/en-
us/download/details.aspx?id=41950
– Microsoft Online Services Module for Windows PowerShell (64-
bit), http://go.microsoft.com/fwlink/p/?linkid=236297