locked
Sharepoint Multi Client Forms Based Authentication RRS feed

  • Question

  • I will be setting up Forms Authentication on a SharePoint Server which will have serveral different client all of whom will have their own site collections. I have set up FBA, which seems to work. Can anyone recommend options for segmenting the server up so different clients cannot access different thing. Someone mentioned multitenancy but it seems complicated. Bear in mind this isn't an enterprise architecture/level of complexity - its just about 10-20 lists/doc libraries a few Silverlight screens and a search screen. Can I just assign a site collection to a group in FBA? I'm a developer rather than an admin so I am fairly new to this.
    Chris
    Saturday, April 16, 2011 2:54 PM

Answers

  • Yes i suggest Multi Tenant too, it is not so complicated when you do it. seriously, also talking best practice then it is the Multi Tenant.

    & about creating Site Collections to groups in FBA, yes you can, no problem in this, but remember you have Search, you will have to configure search to only search within the site collection, so everyone sees only his content.

    I still recommend Multi Tenant, because also the following services can be partitioned and can store Tenant Data:

    • Subscription Settings (not actually partitioned)
    • User Profiles
    • Managed Metadata
    • Business Data Connectivity
    • Search
    • Secure Store
    • Word Automation
    • Project

    The following services do not store tenant data, and do not support Partition Mode:

    • State
    • Access Database
    • Visio Graphics
    • Word Viewing
    • PowerPoint
    • Excel Calculation

      The following services cannot be partitioned and could store tenant data:

    • Web Analytics (this one is site collection based, so it's not a big deal)
    • Usage and Health Data Collection (as above)

    More here: http://www.harbar.net/articles/sp2010mt1.aspx and http://www.c-sharpcorner.com/UploadFile/anavijai/5373/ and http://blogs.msdn.com/b/russmax/archive/2010/04/03/sharepoint-2010-multi-tenant-hosting-part-2-configuring.aspx


    Mai Omar | Senior Solutions Developer | ITEgyptCorp | MCP, MCTS, MCPD, MCITP & MCT Microsoft Certified Trainer | Email: mai_omar_86@live.com | Blog: http://maiomar.itegyptcorp.com
    • Marked as answer by Porter Wang Wednesday, April 20, 2011 2:07 AM
    Saturday, April 16, 2011 3:19 PM
  • IMHO Multi-tenancy is overkill for your requirements. You can just add permissions to roles against each Site Collection. Search will security trim the results, so you shouldn't be worried about users seeing things they shouldn't.

    You can also separate the content databases, and even the Web applications.

    Hope this helps!


    Independant SharePoint Consultant. Feel free to contact me. Blog: http://www.sharepoint.bg/radi Twitter: @RadiAtanassov
    • Marked as answer by Porter Wang Wednesday, April 20, 2011 2:07 AM
    Saturday, April 16, 2011 4:34 PM

All replies

  • Yes i suggest Multi Tenant too, it is not so complicated when you do it. seriously, also talking best practice then it is the Multi Tenant.

    & about creating Site Collections to groups in FBA, yes you can, no problem in this, but remember you have Search, you will have to configure search to only search within the site collection, so everyone sees only his content.

    I still recommend Multi Tenant, because also the following services can be partitioned and can store Tenant Data:

    • Subscription Settings (not actually partitioned)
    • User Profiles
    • Managed Metadata
    • Business Data Connectivity
    • Search
    • Secure Store
    • Word Automation
    • Project

    The following services do not store tenant data, and do not support Partition Mode:

    • State
    • Access Database
    • Visio Graphics
    • Word Viewing
    • PowerPoint
    • Excel Calculation

      The following services cannot be partitioned and could store tenant data:

    • Web Analytics (this one is site collection based, so it's not a big deal)
    • Usage and Health Data Collection (as above)

    More here: http://www.harbar.net/articles/sp2010mt1.aspx and http://www.c-sharpcorner.com/UploadFile/anavijai/5373/ and http://blogs.msdn.com/b/russmax/archive/2010/04/03/sharepoint-2010-multi-tenant-hosting-part-2-configuring.aspx


    Mai Omar | Senior Solutions Developer | ITEgyptCorp | MCP, MCTS, MCPD, MCITP & MCT Microsoft Certified Trainer | Email: mai_omar_86@live.com | Blog: http://maiomar.itegyptcorp.com
    • Marked as answer by Porter Wang Wednesday, April 20, 2011 2:07 AM
    Saturday, April 16, 2011 3:19 PM
  • IMHO Multi-tenancy is overkill for your requirements. You can just add permissions to roles against each Site Collection. Search will security trim the results, so you shouldn't be worried about users seeing things they shouldn't.

    You can also separate the content databases, and even the Web applications.

    Hope this helps!


    Independant SharePoint Consultant. Feel free to contact me. Blog: http://www.sharepoint.bg/radi Twitter: @RadiAtanassov
    • Marked as answer by Porter Wang Wednesday, April 20, 2011 2:07 AM
    Saturday, April 16, 2011 4:34 PM