1

I've configured the FBA authentication on IIS in the following manner:

  1. Created the aspnetdb
  2. Configured the providers in each web.config (application, central admin and Security Token Service Applicaion [STS]).
  3. On the central admin, configured the Claims authentication of the web application to use the providers in the STS.
  4. Configured the people picker wildcard on the provider in the application.

Still, when I go to define a site collection administrator on central admin, it can't find any users.

Notes: Web application is configured to only use FBA.

Edit #1: the providers were configured with different names on each web application (e.g., FBA_Sharepoint _Membership, FBA_CentralAdmin_Membership.... etc)

The problem persists.

Edit #2: I've gave permissions to the aspnet db in MSSQL to all accounts related to sharepoint and the problem persists. All the accounts associated with the application pools (identity) have permission to the database.

The problem persists.

More details:

STS RoleManager:

<roleManager defaultProvider="FBA_STS_RoleProvider"> <providers> <add name="FBA_STS_RoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" applicationName="/" connectionStringName="FBA_STS_ConnectionString" /> </providers> </roleManager>

STS Membership:

<membership defaultProvider="FBA_STS_MembershipProvider"> <providers> <add name="FBA_STS_MembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" applicationName="/" connectionStringName="FBA_STS_ConnectionString" enablePasswordReset="true" enablePasswordRetrieval="false" passwordFormat="Clear" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" /> </providers> </membership>

Central Admin Membership:

<membership defaultProvider="FBA_CentralAdmin_MembershipProvider"> <providers> <add name="FBA_CentralAdmin_MembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" applicationName="/" connectionStringName="FBA_CentralAdmin_ConnectionString" enablePasswordReset="true" enablePasswordRetrieval="false" passwordFormat="Clear" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" /> </providers> </membership>

Central Admin Role Manager:

<roleManager defaultProvider="FBA_CentralAdmin_RoleProvider"> <providers> <add name="FBA_CentralAdmin_RoleProvider" type="System.Web.Security.SqlRoleProvider, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" applicationName="/" connectionStringName="FBA_CentralAdmin_ConnectionString" /> </providers> </roleManager>

Improve this question
10
  • How you created the users in the database? Is the users migrated from someother place or are those newly created users?
    – Amal Hashim
    Commented Jan 9, 2015 at 13:38
  • Does the farm account has permission to the aspnet database?
    – Amal Hashim
    Commented Jan 9, 2015 at 13:39
  • Check sharepoint.stackexchange.com/questions/31377/…
    – Jussi Palo
    Commented Jan 9, 2015 at 14:11
  • @AmalHashim, thanks. I've created the users, through the IIS manager, after configuring the providers. The farm account does have db_owner permissions on the aspnet database.
    – João Tiago Santos
    Commented Jan 9, 2015 at 15:04
  • @AmalHashim, also, the providers were configurated with different names on each web application (e.g., FBA_Sharepoint _Membership, FBA_CentralAdmin_Membership.... etc). I'll edit the question so it mentions this.
    – João Tiago Santos
    Commented Jan 9, 2015 at 15:25

1 Answer 1

Reset to default
0

I created new providers for each web application (central admin, application and security token service), but with the same name. Configured the people picker to use that name and now the people picker works.

I got another issue, but I'll post a new question.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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