Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I'm having a problem trying to add an ASP.NET Membership (SQL Provider) user as a site collection administrator in WSS3.

My user can log into the front end website and can manage their profile (modify and save) using my custom forms, so the actual FBA/ASP.NET Membership system seems to be working correctly.

When I browse to the Site Collection Administrators screen (within the site collection, logged in as a different admin user) and enter the name of my user as 'myprovider:myusername', and then click the Check Names button, the user is validated and it appears that the system has recognised it.

However, when I click OK to add the user as an administrator, I get the following error:

The user or group 'myprovider:myusername' is unknown. at Microsoft.SharePoint.Utilities.SPUtility.FilterValidLoginName(String loginName, SPSite site)

Does anyone know why this might be?

share|improve this question
2  
Did you add FBA settings to Central Administration site? –  Vedran Rasol Jul 26 '11 at 11:19
    
I'm hoping this could be the solution, waiting on hearing back from another developer to see if it has worked. –  RobertDougan Jul 29 '11 at 13:18
    
This was the cause, once I had the Central Admin set up correctly I was able to add users. Thanks for the pointer. –  RobertDougan Aug 4 '11 at 9:32

1 Answer 1

up vote 0 down vote accepted

When configuring FBA it is important to also set Central Administration site and SecurityTokenServiceApplication by using exactly the same settings as on FBA enabled web application.

Details of how to configure FBA can be found here:

http://blogs.technet.com/b/mahesm/archive/2010/04/07/configure-forms-based-authentication-fba-with-sharepoint-2010.aspx

If your web application is set to use Claims Based Authentication with FBA or with some other custom claims enabled it is also common for PeoplePicker control to mark every input as resolved (without actually checking for user) and this can be confusing and can lead to errors as described in this question.

Some more info on PeoplePicker can be found by exploring following links:

http://blogs.technet.com/b/tothesharepoint/archive/2011/02/07/new-understanding-people-picker-and-custom-claims-providers.aspx

http://technet.microsoft.com/en-us/library/gg602068.aspx#architecture

http://technet.microsoft.com/en-us/library/gg602072.aspx

share|improve this answer
    
I just posted my comment as answer and added some extra info. –  Vedran Rasol Aug 4 '11 at 10:28
    
Great, thanks Vedran, some good info there. –  RobertDougan Aug 4 '11 at 11:50

Your Answer

 
discard

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.