In this session, you learn how authentication and authorization work in SharePoint 2013, either when handling direct users’ requests, or running requests for SharePoint apps. In particular, see how to federate with an external Identity Provider like Windows Azure ACS to authenticate users and then authorize them in SharePoint, leveraging claims.
There is one Level 400 session (highest) – guess what’s it about? Right, Authentication.
Here are my session notes.
Classic Authentication is deprecated in SharePoint 2013. So its all about Claims now. The though thing is to map the incoming tokens from the authentication provider to the ones SharePoint use.
Paolo showed an example how to utilize Facebook to log into SharePoint via Azure ACS. As said, he had to map the incoming claims token to SharePoint properties – trust the certificate on the SharePoint site and that’s it basically.
You can create a custom Identity Provider, there is a every well documented example by Steve Peschka.
After the theory Paolo showed us how to utilize this knowledge in combination with apps. This is my favorite diagram about this:
This is crazy stuff – but very powerful.
Session Slides and Recording
Authentication/Security is tough stuff: I did something similar with ADFS for a client, I wish I had this information earlier – it helped me understand what’s happening under the hood. Too bad that there are not that many advanced sessions, I wish there were more. Thanks Paolo for my better understanding about this topic!
Max has led SharePoint implementations for Dax 30 companies since 2009.
Max’s free time is spent on twitter mostly with a good coffee in his hands.
Latest posts by Max Melcher (see all)
- He’s dead, Jim: SharePoint 2013 Search Troubleshooting - October 13, 2014
- Create SharePoint 2010/2013 Search Content Sources – one script to rule them all - July 14, 2014
- What happened to ‘the’ ULSViewer and how to still get it? - June 4, 2014