The Who, What, Why and How of Active Directory Federation Services (AD FS)

slide decks from my session at SharePointalooza 2015

1. The Who, What and Why of Active Directory Federation Services (ADFS)

2. Be Sure To Thank Our Awesome Sponsors!

3. About Me Co-author, SharePoint 2013 Administrators Pocket Guide MCT, MCTIP: SharePoint 2010, MCTS: Project Server 2010 12 years working on the SharePoint platform in a variety of positions. 7 years of instructional/training delivery experience. My blogs: http://summit7systems.com/author/jay.simcox/ http://www.sharepointmechanic.com/ Contact Me: Email: [email protected] Twitter: @ jaysimcox /@ SPHoneyBadger Senior Consultant/Instructor, Summit 7 Systems/Mindsharp Huntsville, AL

4. Work performed in 31 States Employees in 6 States 100% CSAT Satisfaction 2 Microsoft MVPs 30+ Published Books 1 Office Dog About Summit 7 Systems

5. Agenda

6. Agenda

7. The FIRST Question YOU Should be Asking! Is AD FS the right solution for my requirement?

8. Reverse-proxy? Hybrid? Access from outside the corporate network? Access for partners or vendors? Device or role-based access? Single sign on (SSO) IT DEPENDS….

9. Who benefits from ADFS - I? Implementing Organizations Easily share internal resources with external users. Create a role based security model. Possible to reduce overall licensing costs with additional servers roles like Web Application Proxy ( WA-P ). Partner Organizations Easy access to external organization resources

10. Who benefits from ADFS - II? IT Staff Administrators No longer have to manage external user accounts or passwords. Centralized federated partner management. Extensible architecture allows for adding, modifying or creating custom claims to support specific business processes. Developers Leveraging Windows Identity Foundation developers can build .NET applications that rely on ADFS instead of an internal authentication mechanism. These are known as “Claims-Aware” applications.

11. Who Benefits from ADFS - III? End Users SSO experience across multiple applications and platforms. Reduced need for multiple logons Simplified password management (single password across multiple platforms and applications).

12. What IS ADFS? Not new, ADFS has been around since Windows Server 2003 R2. Windows Server 2012 R2 role. Allows for the secure sharing of identity information. Provides secure authentication to multiple systems (SharePoint, Dynamics, Exchange, O365, etc…) Reduces administrative overhead involved with managing “guest” or external AD account.

13. What are the Benefits of ADFS? Allows us to “easily” open applications to external partners. Web based Single Sign On (SSO). Reduced administrative overhead managing guest accounts and passwords. Supports the WS-Federation protocol. Partner or guest user account management by local resources is not required.

14. What are the benefits of ADFS? (contd.) Claim mapping defines claims in terms that each partner organization understands. Claim mappings can be different for each partner organization. Can leverage multiple claim types Identity Claims Group Claims Custom Claims Device Claims

15. ADFS Limitations Not an overly simple implementation. No support for on-premises Exchange. No access to Windows NT token based applications. No access to file shares or print servers. No access to AD resources. No access to Exchange (on-premises only). No connections to servers via RDP. No authentication to “older” web based applications.

16. How does ADFS work? Defines how applications acquire identity information about a user. Designed to specifically overcome limitations in other protocols. Designed to cross boundaries such as security realms, firewalls and different platforms. Takes the burden of authentication off of applications. Requires configuration of multiple components SharePoint Security Token Service (STS) Token-signing certificate Identity Provider ( IdP ) Identity claim Realm SPTrustedIdentityTokenIssuer Relying party security token service Identity provider security token service

17. Authentication in SharePoint Authentication is NOT Authorization Authentication – the process of verifying the identity of a user requesting access to a SharePoint resource. Authorization – the process of identifying an authenticated users permission to access the SharePoint resource. Authentication protocols NTLM Kerberos Claims-based Open Authorization 2.0 ( OAuth ) Server to Server Authentication App authentication

18. NTLM Process The user requests a SharePoint site. SharePoint sends a request for Windows Credentials to the user in the form of a login box asking for a username and password. The end user enters their Windows credentials and submits them to SharePoint. SharePoint validates the users account with AD. SharePoint requests and receives the users group membership from AD. SharePoint creates a SharePoint security token and sends the authorization code and requested web page to the end user.

19. Kerberos Process The Client sends an HTTP (GET) request as an anonymous user. The WFE responds with a 401.2 (unauthorized: Login failed) and with a WWW-Authenticate: Negotiate or WWW-Authenticate: Kerberos header. The client contacts the KDC on the domain controller requesting a Kerberos ticket for the SPN (service-principal-name) referenced by the client browser. If the KDC finds a matching SPN it creates and encrypts a ticket and returns it to the client. The client creates the authenticator and returns it with the ticket to the WFE. The WFE decrypts the ticket and determines identity and checks permissions on the SharePoint server to see what access, if any, is to be granted. If access is permitted IIS contacts the SQL server through the Web Application service. The Web Application service requests a ticket for the SQL server from the KDC. If an SPN is found the KDC returns the ticket which the web application uses to impersonate the user. SQL Server checks the ticket from the Web Application service and validates it and sends the data back to the WFE. .NET compiles the . aspx page and sends it to the users browser.

20. Claims Process The end user hits the SharePoint site generating an HTTP (GET) request. SharePoint redirects the user to the Identity Provider to get a security token. The end user is prompted for credentials by the Identity Provider. The Identity Provider validates the provided credentials with the authentication provider (in this case AD DS) and if successful provides the client a security token. The Identity Provider sends the end user a SAML security token. The end user submits a new request to SharePoint with the SAML token. The SharePoint STS generates the SharePoint security token, the FedAuth cookie and the requested SharePoint site.

21. Claims in A Nutshell Claim: an assertion or statement of something as a fact. Could be any piece of data or information about a user. Digitally signed at creation. Claims must have an attribute to be used with SharePoint Do not rely on applications for authentication. Rely on security token services (STSs). Not just for identities, can also be used for roles and access rights. Commonly defined with Security Assertion Markup Language (SAML)

22. The Token

23. What Would an ADFS implementation look like?

24. What Should I worry About? Search User Profile Service End user experience People-Picker Unique Identifier Authentication method (username/password, smart card, RSASecureId ).

25. Best Practices Use SAN certificates on the WA-P servers. Protect your ADFS servers as if they are Domain Controllers. High availability should always be a part of the design. Especially hybrid deployments.

26. Q & A

27. Be Sure To Thank Our Awesome Sponsors!

28. Thank You for Attending!