SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I believe in SharePoint 2007 you could authenticate a user programatically (without a password) using something like this: FormsAuthentication.RedirectFromLoginPage(username, false);

In SharePoint 2010 since FBA moved to claims we need to use something like this: SPClaimsUtility.AuthenticateFormsUser(site, username, password);

Is there an equivalent using SharePoint 2010 that you can use that does not require a password?

share|improve this question

I think there is a small confusion here.

The RedirectFromLoginPage method comes from System.Web.Security class, which is not a SharePoint class. So, you should be able to call this method even in SharePoint 2010 by specifying using System.Web.Security.

Moreover this method is not used for authenticating a user. It only redirects an authenticated user back to the originally requested URL or the default URL. The parameter username of this method should be an authenticated user. Check the usage here.

Whenever you call RedirectFromLoginPage method, you will be calling it inside the Membership.ValidateUser(username,password) method to authenticate the user first.

Using the method SPClaimsUtility.AuthenticateFormsUser would be preferable.

share|improve this answer
My apologies on the confusion. Is there a way to programatically authenticate a user without requiring the password? – obautista Mar 13 '12 at 1:02
up vote 0 down vote accepted

I ended up writing my own custom membership and roles provider. This allowed me to not have to use the default FBA configuration in SharePoint 2010 that now uses Claims. This article got me started. I then customized to meet my requirements.

share|improve this answer
obautista I'm in the same situation and I already have my own custom membership provider can you tell me how you got it working with your custom provider? from what I can see the claims base authentication generally is like a wrapper around your custom provider. Even if you create a custom method within your custom provider, which doesn't require a password, how were you able to get the claim base authentication to call it and generate a valid token for it? I forgot to add that I need both the normal authentication method that require username and password and the one that doesn't require pass – user9020 Jun 21 '12 at 19:07

You can check if anonymous access is enabled on

Please check this Site

share|improve this answer
This answer does not really help with the scenario above. The question is how to authenticate users, not allow anonymous. – Milen Nov 20 '13 at 12:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.