Planning Extranet Environments with SharePoint 2010


Published on

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 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.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • How do customers think about IDA management? What are the scenarios they are solving for? The lifecycle of identities, credentials and access from hire to retire…Customers are asking us for comprehensive solutions that span identities, credentials, and resources across the enterprise.
  • With automated user provisioning through Forefront Identity Manager, IT can automatically give and update rights to resources and business applications as per the user’s profile. It becomes easy to provision user identity to only those resources and applications which user is suppose to work and prevent from unauthorized use.organizations using Forefront Identity Manager can define policies that automatically create user accounts, mail boxes, and group memberships in real time so that new employees are productive immediately. When a user changes roles within an organization, Forefront Identity Manager automatically makes the necessary changes in heterogeneous target systems to add and remove access rights.For example, if a user moves from a role in sales to a role in marketing, Forefront Identity Manager can remove them from sales-specific groups and add them to marketing-specific groups to deliver appropriate access permissions to perform their job function.
  • With Forefront Identity Manager (FIM), organizations can define automatic policy enforcement for removing user accounts, mail boxes, and group memberships in real time, which minimizes the risk of information leakage from unauthorized access to resources and confidential information. With FIM, de-provisioning for users leaving the enterprise also becomes centralized and less complicated, which makes it easier to ensure complete de-provisioning to handle future compliance audits.For example, if a user leaves the organization, the HR system forwards a de-provisioning request to FIM. FIM follows approval workflow. With the manager’s approval, FIM automatically removes all rights, account information, mail boxes, and memberships from all relevant applications, groups, and different directories.
  • organizations can also use FIM to synchronize e-mail address lists that are maintained by heterogeneous e-mail systems, such as Microsoft Exchange Server 2000, Exchange Server 2007, and Lotus Notes. organizations that have multiple Active Directory Domain Services and Exchange forests can use FIM to build a single address book. This increases the value of identity integration by simplifying collaboration as well as increasing IT control.Note:FIM 2010 provides a simplified single sign on experience through its identity synchronization capabilities, delivering the ability to synchronize passwords across heterogeneous systems.The policy-based management system of FIM manages users’ identity lifecycle and protects corporate assets against misuse as users move between roles or leave the organization.
  • Combining identity data across multiple directories and systems yields automated account reconciliation and consistency management for user accounts, credentials, and attributes. This means organizations with many different directories and other data repositories, such as an HR application, can use Forefront Identity Manager to synchronize user accounts across systems.
  • Active Directory Certificate Services (AD CS) provides an integrated public key infrastructure that enables the secure exchange of information. With strong security and easy administration across the Internet, extranets, intranets, and applications, AD CS provides customizable services for issuing and managing the certificates used in software security systems employing public key technologies.BenefitsIncrease access security with better security than username and password solutions, and verify the validity of certificates using the Online Certificate Status Protocol (OCSP).Reduce cost of ownership by taking advantage of Active Directory integration for enrollment, storage, and revocation processes.Simplify certificate management using a single information store that comes from full integration with Microsoft Management Console.Streamline deployment by enrolling user and computer certificates without user intervention.Client retrieves certificate policy from Active Directory.Client submits certificate request to Certificate Server based on policy.Certificate Server retrieves user information from Active Directory.Certificate Server returns signed digital certificate to the client.
  • Planning Extranet Environments with SharePoint 2010

    1. 1. Planning Extranet Environments with SharePoint 2010<br />Michael Noel<br />Convergent Computing (<br />@MichaelTNoel<br />
    2. 2. Michael Noel<br />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 .<br />Partner at Convergent Computing ( / +1(510)444-5700) – San Francisco Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security<br />
    3. 3. What we’ll cover<br />Why an Extranet?<br />SharePoint 2010 Extranets<br />Extranet Architecture Options<br />Claims-based Authentication<br />Forefront Unified Access Gateway (UAG) for extranets<br />Forefront Identity Manager for Identity Management in an Extranet<br />
    4. 4. Why an Extranet?<br />
    5. 5. Why an Extranet?<br />Security Isolation<br />Isolation of Data<br />Less Exposure, Perimeter Network Scenarios<br />Partner Collaboration<br />Share SP Content with External Partners<br />Control Partner Accounts<br />Anonymous Customer Scenarios are not really Extranets<br />
    6. 6. SharePoint 2010 Extranets<br />Claims-based Authentication Support<br />Multiple Authentication Providers<br />Better Scalability (Services Architecture)<br />Goodbye SSP!<br />Server Groups<br />Services Applications<br />Multiple Authentication Types per Web Application<br />
    7. 7. Sample Extranet Architecture<br />
    8. 8. Design around Security Requirements<br />Less<br />Secure<br />More<br />Secure<br />Scenario 1: Extranet and Internal Users in Single Farm<br />1A: Single Web App / Single Site Collection<br />1B: Single Web App / Separate Site Collections<br />1C: Multiple Web Apps / Content DBs<br />1D: Separate App Pool / Service App Group <br />Scenario 2: Extranet and Internal Users in Single Farm / Separate Trusted Forests<br />Scenario 3: Extranet and Internal Users in Multiple Farms / One-Way Trust<br />Scenario 4: Extranet an Internal Users in Separate Farms / Claims-based Authfor Internal Access to Extranet<br />Scenario 5: Extranet an Internal Users in Separate Farms / No Access for Internal Accounts to Extranet<br />Scenario 6: Separate Farms / AD FS Federation for Extranet Auth<br />
    9. 9. Extranet Scenario 1:Extranet and Internal Users in Single Farm<br />1A: Single Web App / Single Site Collection<br />1B: Single Web App / Separate Site Collections<br />1C: Multiple Web Apps / Content DBs<br />1D: Separate App Pool / Service App Group <br />
    10. 10. Extranet Scenario 2:Extranet and Internal Users in Single Farm / Separate Trusted Forests<br />
    11. 11. Extranet Scenario 3:Extranet and Internal Users in Multiple Farms and Perimeter Network / One-Way Trust<br />
    12. 12. Extranet Scenario 4:Extranet an Internal Users in Separate Farms / Claims-based Auth Provider for Internal Auth to Extranet<br />
    13. 13. Extranet Scenario 5:Extranet an Internal Users in Separate Farms / No Access for Internal Accounts to Extranet<br />
    14. 14. Extranet Scenario 6:Separate Farms / AD FS Federation for Extranet Auth<br />
    15. 15. Extranet Notes<br />
    16. 16. One-Way Trust Scenarios<br />People Picker needs to be configured to crawl domain if it doesn’t trust the domain where the SharePoint farm is installed.<br />Only with STSADM (Rare exception when you can’t use PowerShell)<br />Example Syntax:<br />stsadm.exe -o setapppassword -password AnyPassw0rd<br />stsadm.exe -o setproperty -pnpeoplepicker-searchadforests -pv ",COMPANYABCsvc_sppplpick,Password1;" -url<br />stsadm.exe -o setproperty -pnpeoplepicker-searchadforests -pv ",COMPANYABCsvc_sppplpick,Password1;" -url<br />Syntax is critical<br />Run against all web apps<br />
    17. 17. Design for Clientless Access to SharePoint<br />Services Applications for Extranet Clients:<br />Word Services<br />Excel Services<br />Visio Services<br />Access Services<br />InfoPath Forms Services<br />Allows ‘Clientless’ access to SharePoint content, for Extranet partners without Office<br />
    18. 18. Standard Requirements Apply to Extranets as well<br />SharePoint-aware Antivirus<br />i.e. Forefront Protection for SharePoint<br />SharePoint-aware Backup and Restore<br />i.e. System Center Data Protection Manager (DPM) 2010<br />Rights Management?<br />Active Directory Rights Management Services (AD RMS)<br />
    19. 19. Content Deployment with Extranets<br />
    20. 20. Claims-based Authentication<br />
    21. 21. Claims-Based Auth<br />SharePoint doesn’t actually Authenticate Users, it relies on IIS or other providers<br />SharePoint 2010 Allows for Classic and Claims-based AuthScenarios<br />Classic Authentication is similar to SharePoint 2007<br />Claims based Auth adds the following key benefits:<br />Allows for Multiple Authentication Types per Web Application Zone<br />Removes SharePoint from the Authentication Provider<br />Allows for federation between organizations (AD FS, etc.) scenarios<br />Does not require Kerberos Delegation<br />Remember the difference between Authentication and Authorization…<br />
    22. 22. Classic vs. Claims-based Auth<br />
    23. 23. Mixed-Mode vs. Multi-Authentication<br />
    24. 24. Example: Partner Environment with Multiple Auth Types on single W.A.<br />
    25. 25. Forefront Unified Access Gateway 2010<br />
    26. 26. UAG Architecture<br />Data Center / Corporate Network<br />Exchange<br />CRM<br />SharePoint<br />IIS based<br />IBM, SAP, Oracle<br />Mobile<br />HTTPS / HTTP<br />Home / Friend <br />/ Kiosk<br />Terminal / Remote Desktop Services<br />Layer3 VPN<br />HTTPS (443)<br />Internet<br />DirectAccess<br />Non web<br />Business Partners /<br />Sub-Contractors<br />AD, ADFS, <br />RADIUS, LDAP….<br />NPS, ILM<br />Employees Managed Machines<br />
    27. 27.
    28. 28. What about ISA? (TMG)<br />
    29. 29. What is Forefront Identity Manager?<br />
    30. 30. Identity and Access Management<br />Secure Messaging<br />Secure Endpoint<br />Secure Collaboration<br />Information Protection<br />Identity and Access Management<br />Active Directory®Federation Services<br />
    31. 31. Why FIM for SharePoint?<br />
    32. 32. Manage SharePoint Identities<br />Create Multiple Authentication Providers for SharePoint Farms<br />AD DS Forests (Extranet forests)<br />AD LDS Authentication Providers<br />SQL Table (FBA) Authentication Sources<br />LDAP Providers<br />Etc…<br />Keep those Authentication Providers Managed<br />
    33. 33. Identity Lifecycle Management<br />Create<br />Provision user<br />Provision credentials<br />Provision resources<br />Help Desk<br /><ul><li>“Lost” Credentials
    34. 34. Password Reset
    35. 35. New Entitlements</li></ul>Retire<br />Policy Management<br />De-provision identities<br />Revoke credentials<br />De-provision resources<br />Policy enforcement<br />Approvals and notifications<br />Audit trails<br />Change<br />Role changes<br />Phone # or titlechange<br />Password and PIN reset<br />Resource requests<br />
    36. 36. Identity ManagementUser provisioning for SharePoint and other Applications<br /><ul><li>Policy-based identity lifecycle management system
    37. 37. Built-in workflow for identity management
    38. 38. Automatically synchronize all user information to different directories across the enterprise
    39. 39. Automates the process of on-boarding users</li></ul>ActiveDirectory<br />Extranet Forest<br />Workflow<br />User Enrollment <br />Test Forest<br />FIM<br />FBA Table<br />Approval<br />HR System<br />LOB <br />App<br />VPN<br />Manager<br />User provisioned on all allowed systems<br />
    40. 40. Identity ManagementUser de-provisioning<br /><ul><li>Automated user de-provisioning
    41. 41. Built-in workflow for identity management
    42. 42. Real-time de-provisioning from all systems to prevent unauthorized access and information leakage</li></ul>ActiveDirectory<br />Extranet Forest<br />Workflow<br />User de-provisioned <br />Test<br />Forest<br />FIM<br />FBA<br />Table<br />HR System<br />LOB<br />App<br />VPN<br />User de-provisioned or disabled on all systems<br />
    43. 43. GivenName<br />Samantha<br />sn<br />Dearing<br />title<br />Coordinator<br />mail<br /><br />employeeID<br />007<br />telephone<br />555-0129<br />givenName<br />sn<br />title<br />mail<br />employeeID<br />telephone<br />Identity Synchronization and ConsistencyIdentity synchronization across multiple directories<br />HR<br />System<br />FIM<br />Samantha<br />givenName<br />Samantha<br />sn<br />Dearing<br />Dearing<br />title<br />mail<br />Attribute Ownership<br />employeeID<br />007<br />007<br />telephone<br />FirstName<br />LastName<br />EmployeeID<br />Internal<br />AD<br />givenName<br />Samara<br />sn<br />Darling<br />title<br />Coordinator<br />Coordinator<br />mail<br />employeeID<br />007<br />telephone<br />Identity<br />Data<br />Aggregation<br />Title<br />Extranet<br />AD<br />givenName<br />Sam<br />sn<br />Dearing<br />title<br />Intern<br />mail<br /><br />employeeID<br />007<br />telephone<br />E-Mail<br /><br />LDAP<br />givenName<br />Sammy<br />sn<br />Dearling<br />title<br />mail<br />employeeID<br />008<br />555-0129<br />telephone<br />555-0129<br />Telephone<br />
    44. 44. Identity Synchronization and ConsistencyIdentity consistency across multiple directories<br />FIM<br />HR<br />System<br />givenName<br />Samantha<br />sn<br />Dearing<br />title<br />mail<br />Attribute Ownership<br />employeeID<br />007<br />telephone<br />givenName<br />Bob<br />Samantha<br />Samantha<br />Samantha<br />sn<br />Dearing<br />Dearing<br />Dearing<br />FirstName<br />LastName<br />EmployeeID<br />title<br />Coordinator<br />Coordinator<br />Coordinator<br />Coordinator<br />Internal<br />AD<br />givenName<br />Samara<br />mail<br /><br /><br /><br /><br />sn<br />Darling<br />employeeID<br />007<br />title<br />Coordinator<br />telephone<br />555-0129<br />555-0129<br />555-0129<br />555-0129<br />mail<br />Incorrect or Missing<br />Information<br />employeeID<br />007<br />telephone<br />Identity<br />Data<br />Brokering<br />(Convergence)<br />Title<br />Extranet<br />AD<br />givenName<br />Sam<br />sn<br />Dearing<br />title<br />Intern<br />mail<br /><br />employeeID<br />007<br />telephone<br />E-Mail<br />LDAP<br />givenName<br />Sammy<br />sn<br />Dearling<br />title<br />mail<br />employeeID<br />007<br />telephone<br />555-0129<br />Telephone<br />
    45. 45. Customizable Identity Portal<br />SharePoint-based Identity Portal for Management and Self Service<br />How you extend it<br />Add your own portal pages or web parts<br />Build new custom solutions<br />Expose new attributes to manage by extending FIM schema<br />Choose SharePoint theme to customize look and feel<br />
    46. 46. Customizable Identity Portal<br />Can be used to allow Extranet Partners to Perform Self-Service Management<br />Give control of Account Management to users/administrators of the extranet partner<br />Secure access to portal through VPN/Reverse Proxy<br />Portal in the DMZ<br />Can be used for Self-Service Password Reset (via domain-joined computer)<br />
    47. 47. Strong Authentication—Certificate Authority<br /><ul><li>Streamline deployment by enrolling user and computer certificates without user intervention
    48. 48. Simplify certificate and SmartCard management using Forefront Identity Manager (FIM)
    49. 49. Can be used to automate Certificate management for dual factor auth approaches to SharePoint logins</li></ul>User is validated using multi-factor authentication<br />FIM policy triggers request for FIM CM to issue certificate or SmartCard<br />Certificate is issued to user and written to either machine or smart card<br />SmartCard<br />End User<br />End User<br />FIM CM<br />Active Directory Certificate Services (AD CS) <br />FIM<br />SmartCard<br />User ID andPassword<br />Multi-Factor Authentication<br />FIM Certificate Management (CM) requests certificate creation from AD CS<br />User Enrollment and Authentication request sent by HR System<br />HR System<br />
    50. 50. Real World FIM Usage Scenarios<br />
    51. 51. FIM for Extranet Forest Mgmt<br />Internal AD DS Forest<br />DMZ Extranet AD DS Forest<br />FIM Auto-provisions certain user accounts in Extranet forest and keeps Passwords in Sync to allow Internal users to access/collaborate with Partners<br />FIM allows Self-Service Portal Access for Extranet user accounts in the partner forest<br />Two-factor Auth scenarios, to automate provisioning of user accounts AND certificates to systems<br />
    52. 52. FIM for Role Based Access Control<br />FIM is central to RBAC Strategy<br />Can auto-add users to Groups based on RBAC Criteria<br />HR Defines a user’s access based on their role<br />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.<br />SharePoint Group<br />
    53. 53. Session Summary<br />Understand the Extranet Design Options for 2010<br />Keep Extranet Accounts out of local AD<br />Determine how Identities will be Managed<br />Use FIM for Identity Management, Self-Service, and Provisioning/Deprovisioning of Extranet Accounts<br />Use UAG to secure inbound access to extranets/intranets<br />
    54. 54. Your Feedback is Important<br />Please fill out a session evaluation form drop it off at the conference registration desk.<br />Thank you!<br />
    55. 55. Thanks for attending!Questions?<br />Michael Noel<br />Twitter: @MichaelTNoel<br /><br />