Tag Info

Hot answers tagged

9

"Keyset does not exist" means you need to give your web application pool identity account access to your certificate. Do this in the Certificates Snap In.


6

I havent tried this for claims in SP2010, but in SP2007 this was done for FBA by adding PeoplePickerWildCard element to membership provider in web.config <PeoplePickerWildcards> <clear /> <add key="AspNetSqlMembershipProvider" value="%" /> <add key="fbaMembers" value="%" /> </PeoplePickerWildcards> ...


5

The site will feature regular logon (forms) For this I would recommend to use the Forms base or windows authentication The site will contain some lists where the content is either retrieved from local database or backoffice system OOTB SharePoint Lists can be use to save and retrieve the data (local i.e. saved in SharePoint ContentDB) while ...


5

You can follow steps below: 1) Create a copy of SignOut.aspx in the Layouts folder. Rename it as CustomSignOut.aspx 2) Open the custom page in notepad\designer. In the function _spBodyOnLoad() replace windows.close() with windows.location("YourHomePageRelativeUrl"); 3) Make this page the default sign out page for the web application using below command ...


5

Try to prefix the username with the membership provider info. It would look something like: web.EnsureUser("i:0#.f|membershiprovidername|username");


5

You need to authenticate the connection to SharePoint using the FBA user's credentials. C#: ClientContext clientContext = new ClientContext("http://YourUrlHere"); clientContext.AuthenticationMode = ClientAuthenticationMode.FormsAuthentication; clientContext.FormsAuthenticationLoginInfo = new FormsAuthenticationLoginInfo("username", "password"); ...


5

You may extend the SharePoint Web application with FBA, to create an extranet-facing access point to provide access to the partners. Extending an existing SharePoint Web application provides a separate IIS Web site and you can group external users into a different security domain than internal users. This approach makes it easier to manage different ...


4

In SharePoint 2010 you can actually have dual authentication methods on a site when you use Claims Based authentication. This link should help you get FBA set on on 2010. http://blogs.technet.com/b/speschka/archive/2009/11/05/configuring-forms-based-authentication-in-sharepoint-2010.aspx


4

I can add "X-FORMS_BASED_AUTH_ACCEPTED" in the request header with a value of "f" and then I get the NTLM challenge that I want. This works in both Firefox REST client and when I updated the Java code (the code that makes the request) everything works :-). I found this little tidbit at ...


4

This is typical of a SharePoint implementation. If you think of SharePoint more as a platform than just an application, customization is expected and desired. Whether you proceed with SharePoint as your platform or choose another platform most likely will depend on the resources you can secure to implement this. As SharePoint customization help is in ...


4

Please find a similar issue reported in msdn with FBA authentication and Opera browser. As the post suggests, Opera browser is not on the supported browser list for SharePoint. Chrome isn't on the list either, although that one normally works. Opera has always had issues with SharePoint and it isn't fixed in 2010. Here's the list of approved browsers. ...


4

If you extend a WebApplication you have to have some difference in the url (could be http vs https) otherwise SharePoint has no way of knowing which zone you're in. But if you're using SharePoint 2010 then you don't need to extend to get the behaviour you want. If you enable both Windows and FBA in your zone the default Login Page provides a LogonSelector ...


4

SharePoint 2010: How to Buy You can use SharePoint 2010 to set up intranet, extranet, and Internet sites. Intranet sites are licensed using a Server/CAL (Client Access License) model. SharePoint Server 2010 is required for each running instance of the software, and CALs are required for each person or device accessing a SharePoint Server. ...


4

Extend the Web Application to create two zones - one can be Windows Authentication only, that will allow your content to be crawled. The second can be FBA only, allowing the users to login directly.


4

Do the following powershell command: $sts = Get-SPSecurityTokenServiceConfig $sts.FormsTokenLifeTime = (New-TimeSpan -minutes 30) $sts.Update() Get-SPSecurityTokenServiceConfig


4

You need to put the page in its own library, set the anonymous access for the site to 'Lists and Libraries'. Then you need to allow anonymous access for the single library. If you don't want to turn anonymous access on at all, then you'll have to create your login page as an application page (and this is how you should be creating a login page imho). The ...


4

Tools For use: 1. FBA Configuration Manager for SharePoint 2013 – Author and Credit goes to Steve Peschka. The download comes with a ReadMe file. Please read it, since you need to register the WSP that comes with it. SharePoint 2013 FBA Pack – Author and Credit goes to Chris Coulson. Here is the documentation that will tell you how to ...


3

Your client (the program consuming the service) needs to pass a NetworkCredential object. With integrated auth, this just happens. For FBA, you need to create a new object and put in the credentials. For claims auth, you need to leverage the Identity Framework.


3

It can be achieved by editing the permission level for a group and revoking the View user information permission.


3

Registering the FBA provider with Central Administration allows you to set the Site Collection Administrator to an FBA user. Additionally you might be needing it if you want to use User Profiles or Audiences with FBA users.


3

Here you go, Three fantastic FBA articles on MSDN for SharePoint. More here.


3

My guess is that you didn't set claims provider to be default membership and role provider. This is common mistake and I reproduced exactly the same error on my machine. After setting up FBA providers in web.config (most likely with IIS manager) in most explanations next step is to set FBA provider as default membership and role provider. This is 'required' ...


3

I don´t have any good answer to your problem, but I can give you a tip of checking out my collegue MVP Wictor Wiléns great blog post about LiveID configuration divided in three series and see if you can get any ideas from that. Part 1 - http://www.wictorwilen.se/Post/Visual-guide-to-Windows-Live-ID-authentication-with-SharePoint-2010-part-1.aspx Part 2 - ...


3

You could create an application page or web part and deploy to your SharePoint site. On that page (or web part) add a CreateUserWizard control.


3

My bet is the following: when looking at the user profiles in your user profile application, your user profiles have a (mapped) "name" field that are either empty or contain the loginname. That name field is used to display the display username. When looking at the user profile property "name", you can see that it's internal name is "PreferredName" When ...


3

You will find entries similar to the following in the section of the web.config for your web application or in the root web.config if you configured FBA at the IIS root. You can change the name(s) directly in the web.config file. <roleManager> <providers> <add name="FBARoleProvider" ...


3

My own answer to my question: I gave Full Read to All Authenticated Users on the web application level then added All Authenticated Users to Site Members.


3

Try this... SPClaimsUtility.AuthenticateFormsUser( Context.Request.UrlReferrer, UserName.Text, Password.Text);


3

The functionality that IE is attempting is actually Office trying to authenticate the user on it's own against SharePoint. Chrome/FireFox doesn't have this level of integration and therefore just opens the document. You can get around this by disabling Client Integration in central admin (Application Management > Authentication Providers I think, been a ...



Only top voted, non community-wiki answers of a minimum length are eligible