SharePoint Farm - Claims Based Authentication Problems

I have a SharePoint farm with 2 WFE servers(SH01 and SH02) and 1 Application server(SH03) where there's the Central Admin. When I create a WebApplication with Windows Authentication I can access it normally in both address
http://SH01:10000 and
http://SH02:10000. When I create a WebApplication with Claims Based Authentication enabling FBA when I try to access it with the address above occurs an error:

The WebApplication at http://SH01:10000/ could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping
to the intended application.

I have noticed that the difference between authentication is that FBA redirect to "_login/" when I can choose what type of authentication I want to login(In this case Windows or Forms).

Are there some extra configuration that I have to do to solve this problem?

Hi,
Im working in integrating LiveID authentication in my Sharepoint site. Live id gives back a token of the user with which i created a dummy profile using MembershipProvider.CreateUser. Now i have to auto login the user with the profile
i created, i mean i have to force login to my sharepoint site using the created dummy user details without asking the user to give username n password.Any suggestion will be a great help for me to proceed.
Thanks
Saravanan Michael

Hi,
I have CBA setup successfully on my sites. One site is setup for anonymous access and I have disabled "client integration" on that web application.
I have a list of MS Office documents on a wiki. When I click on one I am asked to either save or open or cancel. Saving works fine but when I choose open, it launches the associated MS Office app. I am then prompted for a login from CBA.
I can click cancel and the logon screen appears again. After clicking cancel the 2nd time the document appears in the MS Office app, Word in this case.
My question is how do I prevent my users from being prompted for a CBA login when clicking on these files and opening them in the native app on their machine?
--TR

I have custom web service developed (it is running out of sharepoint context but on the machine where sharepoint server 2010 is installed). This web service should get SharePoint file content using file URL and some specific user credentials. So in case
user doesn't have access to the file some exception should be thrown. Otherwise content should be returned.

Learn how claims-based identity provides a common way for applications to acquire identity information from users inside their organization, in other organizations, and on the Internet. (Length: 23:46)

I'm about to setup a web application to host a public facing website. Internal staff will authenticate to the site via Active Directory and we may have a need to allow external users to access "authenticated" parts of the site. To authenticate them we plan
to use Windows Live ID.
With that in mind,:
is it better to set the web application up to use claims based authentication from the start rather than having to change it later?
is there anything available as of yet to setup SharePoint 2010 to authenticate against Windows Live ID using claims based authentication?

So this is really an outside the normal question and I am hoping someone has some thoughts. I am going to be upgrading a MOSS 2007 farm to MSS2010. I have to move hardware so I will be using the content database attach method for upgrade. The site is current
extended to a second IIS Application to support both window and Forms based authentication. Since this is an intranet, unique security is used at the site level (and occasionally at the doc lib level).
I want to take advantage of Claims Based Authentication (and use one URL, plus other benefits). I am well aware that that claims based token is not the same as the windows token even though the NTLM user is really the same. Thus that is what presents the
issue. I need to "migrate" all of my current NTLM-Classic users to claims based.
My first thought is to read the users added to each site (actually role assignments), find all users that have the domain name at the beginning of the member name and add a new users (appending the i:0#.w| to the beginning of the loginname) to the site.
This works beautifully and is succesful. The problem arises in the that the role assignments contains SharePoint groups (which we don't use much) and AD groups. the SharePoint groups are ok (yes, I have to migrate the users in them too, but no problem). The
AD groups are added via SID when it is claims based. This presents the probl

This TechNet article does a great job describing how to
Configure forms-based authentication for a claims-based Web application using PowerShell. However, it glosses over editing the web.config file by just saying "Find the
<Configuration> <system.web> section and add the following entry:"
Is it possible to edit the web.config file using PowerShell using the IIS PowerShell snapin or can I just edit the web.config file as a xml document?
This succeeds in adding the element, but only with the name and type. It does not add the connectionStringName or the applicationName
import-module webadministration
Add-WebConfiguration /system.web/membership/providers "IIS:\sites\[site name]" -value @{name="FBAMembershipProvider";`
type="System.Web.Security.SqlMembershipProvider, System.Web, Version= 2.0.0.0, Culture= neutral, PublicKeyToken= b03f5f7f11d50a3a";`
connectionStringName="FBAconn";`
applicationName="/"}
Does anyone any suggestions on a direction to go to add the membership providers and role providers in the web.config using PowerShell?
This is very frustrating because I can do it manually, I can do it through the UI in IIS Manager, I can do it using appcmd, but no matter what I do, I can't get it to work using PowerShell.

Hi
We have sharepoint 2007 site deployed on Windows server 2008, IIS 7.0. We extended the web application to enable forms based authentication referring to link
http://msdn.microsoft.com/en-us/library/bb975136(office.12).aspx#MOSS2007FBAPart1_Intro, we selected
Kerberos instead of NTLM, behavior is like, when user tries to login into the site using OOB login.aspx, user again gets redirected to the login page.
We tried to extend the web application again but this time we selected NTLM, but this time farm account (also is application pool identity) is not able login and exhibits same behavior as above, but for other users we are able to login.
Has anyone come across this behavior? can anyone please guide me in correct the behavior?
Regards,
RK
Radhakrishna