With the new SharePoint App model running outside the SharePoint worker process it introduces new authentication models. As a developer you don't want to build multiple versions of the same app implementing each authentication model separately. This session explains the differences between securing SharePoint apps with OAuth in Office 365 and S2S High Trust in on-premise deployments. You will learn how to build a single app that will run on-premise, online and hybrid SharePoint environments.

1. Developing hybrid SharePoint apps that
run on-premise and in the cloud

3. About Bram
http://bramdejager.wordpress.com
@bramdejager
bram.de.jager@macaw.nl

4. Agenda

5. Another authentication model?!
Why do we need a new
authentication model?

7. Where does the new App model fit
in?

8. Customization Options
Sandbox
 Hosted in isolated
process
 Limited server side
SharePoint API
access
 No external
service calls
Farm SharePoint
Apps
 Full trust solutions
 Customizations to
file system of
servers
 Hosted in same
process as
SharePoint
 Server side
SharePoint API
access
 Classic model from
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

Deprecated in
SharePoint 2013

9. Hybrid Scenarios

10. Cloud, On-Premise, and Hybrid
•
•
•
Azure AD
Office 365App
App SharePoint

11. SharePoint-hosted apps on-prem and online

12. Inside OAuth

13. Access token and issuer

14. OAuth-authenticated request

15. Decoded access token

16. Online authentication

17. On-premise authentication

18. Building a High-Trust (S2S) app on-premise

19. Hybrid Apps

20. Hybrid app

21. Building a Hybrid app

22. Wrap up

23. Summary

24. Contact
www.macaw.nl
Bram.de.Jager@macaw.nl
bramdejager.wordpress.com
@bramdejager

25. THANK YOU