locked
Host named site collection and FBA RRS feed

  • Question

  • Hi,

    I'm trying to create a farm with alot of "Web application" or "Site Collection", because the amount of sites could be 1000+ i thought that host named site collection was the way to approve this implementation. Every site will only be bound to a couple of users, so a web application to each site, would demand a really huge farm :(

    But i'm facing a big problem using host named site collections, because I every host named site collection to use it's own FBA provider, to be sure, that only each sites users, can use the users combined to it's site, I need to create a FBA provider at every site.

    So my actual question is:
    Is it possible to have a different FBA provider on each site, in a host named site collection?

    Cheers from Denmark
    Lars

    Sunday, January 23, 2011 8:27 AM

Answers

  • Hi,

    You have to configure FBA seperately for each site.

    Only for Central Admin it remains common.

    For each site you have to make changes in its own web.config file.

    To configure FBA you can refer

    http://www.simple-talk.com/dotnet/windows-forms/configuring-forms-authentication-in-sharepoint-2007/


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    • Marked as answer by Leoyi Sun Tuesday, February 8, 2011 7:10 AM
    Sunday, January 23, 2011 2:39 PM
  • How dod you create host header sites ?

    Please extend an existing site with host header using SharePoint Central Admin wizard , which will generate seperate web.config file for each host header site.

    i.e Site1 with server name = http://servername1

    Extend it to http://hostheader which will create a seperate web.config in IIS


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    • Edited by Pratik Vyas Monday, January 24, 2011 8:29 AM add
    • Marked as answer by Leoyi Sun Tuesday, February 8, 2011 7:10 AM
    Monday, January 24, 2011 8:27 AM

All replies

  • Hi,

    You have to configure FBA seperately for each site.

    Only for Central Admin it remains common.

    For each site you have to make changes in its own web.config file.

    To configure FBA you can refer

    http://www.simple-talk.com/dotnet/windows-forms/configuring-forms-authentication-in-sharepoint-2007/


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    • Marked as answer by Leoyi Sun Tuesday, February 8, 2011 7:10 AM
    Sunday, January 23, 2011 2:39 PM
  • Hi Pratik,

    Thanks for you fast response.

    I just really completely understand your answer. In my experience with host-named site collections architecture, there only is one Web Application, which means there only is one web.config. If you modifiy the web.config to use one provider, all the host-named sites, are then using the same provider, which means they are using the same group of users.

    My needs is, that every host-named site collection in the same web application, are using different Membership providers, to control which users a host-name site collection can use. Meaning that site 1 users can't use site 2 users. Therefore they need individual membership providers in each host-named site collection.

    Sunday, January 23, 2011 2:48 PM
  • How dod you create host header sites ?

    Please extend an existing site with host header using SharePoint Central Admin wizard , which will generate seperate web.config file for each host header site.


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    Monday, January 24, 2011 8:27 AM
  • How dod you create host header sites ?

    Please extend an existing site with host header using SharePoint Central Admin wizard , which will generate seperate web.config file for each host header site.

    i.e Site1 with server name = http://servername1

    Extend it to http://hostheader which will create a seperate web.config in IIS


    Regards, Pratik Vyas | SharePoint Consultant | http://sharepointpratik.blogspot.com/
    • Edited by Pratik Vyas Monday, January 24, 2011 8:29 AM add
    • Marked as answer by Leoyi Sun Tuesday, February 8, 2011 7:10 AM
    Monday, January 24, 2011 8:27 AM
  • Hi Pratik,

    I don't think your knowledge about SharePoint in that area is enough to answer my question.

    What you are talking about is extending or creating new web applications, which as you say, generates new root folders with new web.config.

    But it's possible in SharePoint to generate a web application, where you in this newly created web application, creates alot of site collections, with it's on host header. This procedure, dosn't generate new web.config files, because every host header is in a specific site collection, and not in every web applications.

    If you would like to know more informationer about host-named site collections, please read http://technet.microsoft.com/en-us/library/cc424952.aspx

    The approach to this problem, with a Web Application for each site, will have a problem when i have generated 600 web application in one and same farm.
    Host-named site collection make is possible to create 300 sites in one web application.

    Wednesday, January 26, 2011 6:13 PM
  • Lars,

    Did you find a solution?  I am trying to do something similar.  Thanks...

    Wednesday, March 30, 2011 7:03 PM
  • > I don't think your knowledge about SharePoint in that area is enough to answer my question.

    This is unnecessarily offensive and will not encourage anyone in future to bother trying to answer your posts.

    Try in future to avoid this sort of abusive and totally unnecessary comment.

    Moderator


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Thursday, March 31, 2011 7:00 AM