SharePoint 2010, Web.Config, and Forms/Claims Based Authentication question.
Greetings all!
I've got a question, and I hope the answer is simple (don't we all!). Before setting up claims based authentication (CBA) in our production environment, we installed SharePoint 2010 as a standalone installation on a server that was separate from the farm. The web.config file was modified to list the membership and role providers, for FBA (Forms Based Authentication), which we then proceeded to set up CBA.
We're trying to do the same thing on our production environment, but we seem to have hit a snag...
Now, when trying to set up FBA and CBA in our production farm (which is newly upgraded from SP2007 to SP2010), the virtual directories have seem to have disappeared! When we browse to C:\inetpub\wwwroot\wss\, there is only one virtual directory (which has a web.config file), but we've figured out (by breaking tags in the web.config file to see which sites broke) that this directory belongs to central administration.
But when setting up claims based authentication, we need to edit more than just one web.config file (according to the steps that we followed previously).
My colleagues and I read on a blog somewhere that a SharePoint 2010 server farm takes the web.config files and stuffs them into the database (which I guess is in preparation for fully using the .NET 4.0 framework, although this is just a rumor that I read and have no facts with which to back it up). Regardless of that, if upgrading our 2007 Sharepoint farm to 2010 stuffed our web.config files into the database (which I'm assuming would be the SP config database?), how in the world are you supposed to read/write to it?
We found some code online for a custom .aspx page that you access via http://servername:<central admin port>/_admin/webconfig.asp
I've got a question, and I hope the answer is simple (don't we all!). Before setting up claims based authentication (CBA) in our production environment, we installed SharePoint 2010 as a standalone installation on a server that was separate from the farm. The web.config file was modified to list the membership and role providers, for FBA (Forms Based Authentication), which we then proceeded to set up CBA.
We're trying to do the same thing on our production environment, but we seem to have hit a snag...
Now, when trying to set up FBA and CBA in our production farm (which is newly upgraded from SP2007 to SP2010), the virtual directories have seem to have disappeared! When we browse to C:\inetpub\wwwroot\wss\, there is only one virtual directory (which has a web.config file), but we've figured out (by breaking tags in the web.config file to see which sites broke) that this directory belongs to central administration.
But when setting up claims based authentication, we need to edit more than just one web.config file (according to the steps that we followed previously).
My colleagues and I read on a blog somewhere that a SharePoint 2010 server farm takes the web.config files and stuffs them into the database (which I guess is in preparation for fully using the .NET 4.0 framework, although this is just a rumor that I read and have no facts with which to back it up). Regardless of that, if upgrading our 2007 Sharepoint farm to 2010 stuffed our web.config files into the database (which I'm assuming would be the SP config database?), how in the world are you supposed to read/write to it?
We found some code online for a custom .aspx page that you access via http://servername:<central admin port>/_admin/webconfig.asp
ASKER
It's worth a shot! I'll try it in the morning.
This is what I love about the power of the internet - people have the capability to find things that others (using very similar search terms) may not!
It still gets on my nerves that, if what I'm trying to understand is true, SharePoint 2010 "virtualized" the web.config files by putting them into the database, with no direct way to view what configurations are in it, and no way to directly edit it unless you use someone's home-brew coded applications.
It just seems like a bad way to do business.
This is what I love about the power of the internet - people have the capability to find things that others (using very similar search terms) may not!
It still gets on my nerves that, if what I'm trying to understand is true, SharePoint 2010 "virtualized" the web.config files by putting them into the database, with no direct way to view what configurations are in it, and no way to directly edit it unless you use someone's home-brew coded applications.
It just seems like a bad way to do business.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great job!
http://blogs.technet.com/b/speschka/archive/2010/07/28/sharepoint-2010-forms-based-authentication-configuration-manager.aspx