New answers tagged claims-based-auth
look alike know issue with one of the security update. You need to either uninstall the following hotfix(Security Update for Microsoft Windows (KB2756920) from server. other is apply this hotfix.http://support.microsoft.com/kb/2637518 Source: Secure Token Service (STS) Missing Method – KB2752920 if above failed try this one: Unable to Activate Security ...
Instead of a network credential, you will need a SharePoint Online Credential: http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.client.sharepointonlinecredentials_members(v=office.15).aspx
As you have found, configuring FBA is not trivial. MANY posts I have found just plain don't work. The best I have found is Mirjam's. She has two, I have used the one for SQL FBA and it works every time. Here is the link to her post on AD FBA: http://sharepointchick.com/archive/0001/01/01/configuring-claims-and-forms-based-authentication-for-use-with-an.aspx ...
There seems to be some confusion because Forms-based Authentication IS claims-based authentication too. As a matter of fact, the default authentication method for SharePoint 2013 is claims-based authentication, which include 3 forms of authentication: Windows, FBA and Trusted Providers (i.e. SAML tokens) Also, SharePoint has NEVER been responsible for ...
Use claims based authentication for web application and have your client send SAML tokens . The client(Identity Provider) can send you (email,role claims) and Sharepoint (Service Provider) can trust them .After establishing the trust , add the users to sharepoint group so the user can access your site. By using SAML the SSO requirement is also satisfied.
Top 50 recent answers are included