Organizations planning for Extranet access to SharePoint 2010 or faced with providing access to an Intranet from multiple internal authentication platforms often find it challenging to properly architect SharePoint for extranets, to isolate content, and to manage identities across disparate systems. The complexity involved in understanding how to isolate content from a security perspective but still provide for a collaborative space for end users is complex, and if not done correctly can lead to security breaches and confusion. This session focuses on understanding the various extranet models for SharePoint 2010 and providing real world guidance on how to implement them. Covered are extranet content models and extranet authentication options, including Claims-based authentication and also covering advanced options using tools such as Microsoft's Forefront Identity Manager (FIM) 2010 to centralize identity management to SharePoint 2010 farms, allowing for better control, automatic account provisioning, and synchronization of profile information across multiple SharePoint authentication providers. • Review Extranet design options with SharePoint 2010 • Understand the need for identity management across SharePoint farms • Examine real world deployment guidance and architecture for SharePoint environments using multiple authentication providers

1. 17-20 OCTOBER 2011 DURBAN ICC

2. Collaborating with Extranet Partners on SharePoint 2010 OFC306 Michael Noel – Convergent Computing

3. Michael Noel Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles . Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security

4. What we’ll cover Why an Extranet? SharePoint 2010 Extranets Extranet Architecture Options Claims-based Authentication Forefront Unified Access Gateway (UAG) for extranets Forefront Identity Manager for Identity Management in an Extranet

5. Why an Extranet?

6. Why an Extranet? Security Isolation Isolation of Data Less Exposure, Perimeter Network Scenarios Partner Collaboration Share SP Content with External Partners Control Partner Accounts Anonymous Customer Scenarios are not Extranets

7. SharePoint 2010 Extranets Claims-based Authentication Support Multiple Authentication Providers Better Scalability (Services Architecture) Goodbye SSP! Server Groups Services Applications Multiple Authentication Types per Web Application

8. Sample Extranet Architecture

9. Design around Security Requirements Less Security More Security Scenario 1: Extranet and Internal Users in Single Farm 1A: Single Web App / Single Site Collection 1B: Single Web App / Separate Site Collections 1C: Multiple Web Apps / Content DBs 1D: Separate App Pool / Service App Group Scenario 2: Extranet and Internal Users in Single Farm / Separate Trusted Forests Scenario 3: Extranet and Internal Users in Multiple Farms / One-Way Trust Scenario 4: Extranet an Internal Users in Separate Farms / Claims-based Authfor Internal Access to Extranet Scenario 5: Extranet an Internal Users in Separate Farms / No Access for Internal Accounts to Extranet Scenario 6: Separate Farms / AD FS Federation for Extranet Auth

10. Extranet Scenario 1:Extranet and Internal Users in Single Farm 1A: Single Web App / Single Site Collection 1B: Single Web App / Separate Site Collections 1C: Multiple Web Apps / Content DBs 1D: Separate App Pool / Service App Group

11. Extranet Scenario 2:Extranet and Internal Users in Single Farm / Separate Trusted Forests

12. Extranet Scenario 3:Extranet and Internal Users in Multiple Farms and Perimeter Network / One-Way Trust

13. Extranet Scenario 4:Extranet an Internal Users in Separate Farms / Claims-based Auth Provider for Internal Auth to Extranet

14. Extranet Scenario 5:Extranet an Internal Users in Separate Farms / No Access for Internal Accounts to Extranet

15. Extranet Scenario 6:Separate Farms / AD FS Federation for Extranet Auth

16. Extranet Notes

17. One-Way Trust Scenarios People Picker needs to be configured to crawl domain if it doesn’t trust the domain where the SharePoint farm is installed. Only with STSADM (Rare exception when you can’t use PowerShell) Example Syntax: stsadm.exe -o setapppassword -password AnyPassw0rd stsadm.exe -o setproperty -pnpeoplepicker-searchadforests -pv "domain:companyabc.com,COMPANYABCvc_sppplpick,Password1;domain:extranetabc.com" -url https://extranet.companyabc.com stsadm.exe -o setproperty -pnpeoplepicker-searchadforests -pv "domain:companyabc.com,COMPANYABCvc_sppplpick,Password1;domain:extranetabc.com" -url https://spcaext.companyabc.com Syntax is critical Run against all web apps

18. Design for Clientless Access to SharePoint Services Applications for Extranet Clients: Word Services Excel Services Visio Services Access Services InfoPath Forms Services Allows ‘Clientless’ access to SharePoint content, for Extranet partners without Office

19. Standard Requirements Apply to Extranets as well SharePoint-aware Antivirus i.e. Forefront Protection for SharePoint SharePoint-aware Backup and Restore i.e. System Center Data Protection Manager (DPM) 2010 Rights Management? Active Directory Rights Management Services (AD RMS)

20. Content Deployment with Extranets

21. Claims-based Authentication

22. Claims-Based Auth SharePoint doesn’t actually Authenticate Users, it relies on IIS or other providers SharePoint 2010 Allows for Classic and Claims-based AuthScenarios Classic Authentication is similar to SharePoint 2007 Claims based Auth adds the following key benefits: Allows for Multiple Authentication Types per Web Application Zone Removes SharePoint from the Authentication Provider Allows for federation between organizations (AD FS, etc.) scenarios Does not require Kerberos Delegation Current limitations with Claims-based auth involve SQL Reporting Services, PowerPivot, PerformancePoint, and other SQL tools that require delegation. These appear to be fixed in SQL 2012. Remember the difference between Authentication and Authorization…

23. Classic vs. Claims-based Auth

24. Mixed-Mode vs. Multi-Authentication

25. Example: Partner Environment with Multiple Auth Types on single W.A.

26. Forefront Unified Access Gateway

27. UAG Architecture Data Center / Corporate Network Exchange CRM SharePoint IIS based IBM, SAP, Oracle Mobile HTTPS / HTTP Home / Friend / Kiosk Layer3 VPN Terminal / Remote Desktop Services HTTPS (443) Internet DirectAccess Non web AD, ADFS, RADIUS, LDAP…. Business Partners / Sub-Contractors NPS, ILM Employees Managed Machines

29. What about TMG? (New ISA)

30. Forefront Identity Manager

31. Identity and Access Management Secure Messaging Secure Endpoint Secure Collaboration Information Protection Identity and Access Management Active Directory®Federation Services

32. Manage SharePoint Identities Create Multiple Authentication Providers for SharePoint Farms AD DS Forests (Extranet forests) AD LDS Authentication Providers SQL Table (FBA) Authentication Sources LDAP Providers Etc… Keep those Authentication Providers Managed

34. Built-in workflow for identity management

35. Automatically synchronize all user information to different directories across the enterprise

36. Automates the process of on-boarding usersActiveDirectory Extranet Forest Workflow User Enrollment Test Forest FIM FBA Table Approval LOB App VPN HR System Manager User provisioned on all allowed systems

38. Built-in workflow for identity management

39. Real-time de-provisioning from all systems to prevent unauthorized access and information leakageActiveDirectory Extranet Forest Workflow User de-provisioned Test Forest FIM FBA Table LOB App VPN HR System User de-provisioned or disabled on all systems

40. GivenName Samantha sn Dearing title Coordinator mail someone@example.com employeeID 007 telephone 555-0129 givenName sn title mail employeeID telephone Identity Synchronization and ConsistencyIdentity synchronization across multiple directories HR System FIM Samantha givenName Samantha sn Dearing Dearing title mail employeeID 007 007 telephone Attribute Ownership Internal AD givenName Samara sn Darling title Coordinator Coordinator mail employeeID 007 FirstName LastName EmployeeID telephone Identity Data Aggregation Extranet AD givenName Sam sn Dearing title Intern mail someone@example.com employeeID 007 telephone Title someone@example.com LDAP givenName Sammy sn Dearling title mail employeeID 008 555-0129 telephone 555-0129 E-Mail Telephone

41. Identity Synchronization and ConsistencyIdentity consistency across multiple directories FIM HR System givenName Samantha sn Dearing title mail employeeID 007 telephone givenName Bob Samantha Samantha Samantha sn Dearing Dearing Dearing Attribute Ownership title Coordinator Coordinator Coordinator Coordinator Internal AD givenName Samara mail someone@example.com someone@example.com someone@example.com someone@example.com sn Darling employeeID 007 title Coordinator telephone 555-0129 555-0129 555-0129 555-0129 mail Incorrect or Missing Information employeeID 007 FirstName LastName EmployeeID telephone Identity Data Brokering (Convergence) Extranet AD givenName Sam sn Dearing title Intern mail someone@example.com employeeID 007 telephone Title LDAP givenName Sammy sn Dearling title mail employeeID 007 telephone 555-0129 E-Mail Telephone

42. Customizable Identity Portal SharePoint-based Identity Portal for Management and Self Service How you extend it Add your own portal pages or web parts Build new custom solutions Expose new attributes to manage by extending FIM schema Choose SharePoint theme to customize look and feel

44. Simplify certificate and SmartCard management using Forefront Identity Manager (FIM)

45. Can be used to automate Certificate management for dual factor auth approaches to SharePoint loginsUser is validated using multi-factor authentication FIM policy triggers request for FIM CM to issue certificate or SmartCard Certificate is issued to user and written to either machine or smart card SmartCard End User End User FIM CM FIM Certificate Management (CM) requests certificate creation from AD CS User Enrollment and Authentication request sent by HR System Active Directory Certificate Services (AD CS) FIM SmartCard User ID andPassword Multi-Factor Authentication HR System

46. FIM for Extranet Forest Mgmt Internal AD DS Forest DMZ Extranet AD DS Forest FIM Auto-provisions certain user accounts in Extranet forest and keeps Passwords in Sync to allow Internal users to access/collaborate with Partners FIM allows Self-Service Portal Access for Extranet user accounts in the partner forest Two-factor Auth scenarios, to automate provisioning of user accounts AND certificates to systems

47. FIM for Role Based Access Control FIM is central to RBAC Strategy Can auto-add users to Groups based on RBAC Criteria HR Defines a user’s access based on their role FIM auto-adds that user to specific Role Groups in AD DS, which are tied to SharePoint Groups that have the rights that that role group requires. SharePoint Group

48. Session Summary Understand the Extranet Design Options for 2010 Keep Extranet Accounts out of local AD Determine how Identities will be Managed Use FIM for Identity Management, Self-Service, and Provisioning/Deprovisioning of Extranet Accounts Use UAG to secure inbound access to extranets/intranets

49. http://microsoftvirtualacademy.com Submit your session evaluation for a chance to win! Sponsored by MVA

50. Creating the future together

51. Thanks for attending!Questions? Michael Noel Twitter: @MichaelTNoel www.cco.com Slides: slideshare.net/michaeltnoel