Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm having a really difficult time trying to get my Sharepoint site to use Forms Authentication. I've tried using an ActiveDirectoryMembershipProvder and the LDAP equivalent but both of them seem absolutely unable to find any users from ActiveDirectory in any of the "peoplefinder" type of areas.

In Web.config for the admin section I have this:

<membership defaultProvider="ADMembershipProvider">
<providers>
 <add   name="ADMembershipProvider"
      	type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0,  Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
      	connectionStringName="ADConnectionString" /> 
</providers>
  </membership>

And then a little later this:

<connectionStrings>
    <add name="ADConnectionString" connectionString="LDAP://dc.ourcompany.com/dc=ourcompany,dc=com,ou=Ourcompany,ou=UK,ou=Townville,ou=Users" />
</connectionStrings>

The content of the connectionstring is right out of ADExplorer, but whether that makes it right or not, I don't really know, AD is not my speciality.

I have tried having the user specifed in the <provider> tag and not, neither of which appears to have caused a problem.

When I try to add a user to the site that I am configuring this authentication on, I cannot make it find anyone from the domain. I have tried the following ways of saying it:

  • ADMembershipProvider:username
  • ADMembershipProvider:username@ourcompany.com
  • ADMembershipProvider:OURCOMPANY\username
  • username@ourcompany.com
  • OURCOMPANY\username
  • username

None of those appear to have made any difference.

The really frustrating thing is that neither Sharepoint's logs ( set to Verbose and my god to they mean that ) nor the system Event Log seem to give any indication of a problem, they just don't do anything.

Is there an obvious problem here and if not, is there an easy way I can break things down a little to figure out where in the process it is failing?

share|improve this question
    
My assumption is you are trying to authenticate AD users externally, otherwise you shouldn't be using FBA. If you have ISA Server, it can handle this process for you. –  shufler Sep 4 '09 at 23:53
    
I was actually trying to authenticate them internally, but needed FBA because I was trying to replicate an issue that a customer was having with some software that talks to sharepoint. –  glenatron Nov 11 '09 at 13:12
add comment

4 Answers 4

up vote 1 down vote accepted

I recently set up FBA for my site. I followed this document and it was absolutely flawless. I faced the similar issue you faced but i found out later that i did some mistakes in configuring it the CA's configurationn file.

share|improve this answer
    
This looks really helpful. I've not done anything with this for a fwe months, but I'm going to call this the answer... –  glenatron Feb 23 '10 at 16:49
add comment

Have you tried following this document?

share|improve this answer
    
I have indeed, or at least parts of it, I was also quite closely guided by these two: MSDN on forms - msdn.microsoft.com/en-us/library/ms998360.aspx and this one on AD, forms and Sharepoint: dattard.blogspot.com/2008/11/active-directory-forms-based.html –  glenatron Jul 7 '09 at 15:33
add comment

Have you ensured your provider name is set in your PeoplePickerWildcards element in the web.config? i.e.:

<PeoplePickerWildcards>
  <clear />
  <add key="ADMembershipProvider" value="%" />
</PeoplePickerWildcards>

This will need to be set in the web.config for the application and the necessary entries made in the web.config for the WSS admin application if you are trying to set up anything there.

share|improve this answer
    
I was really excited by this response because it sounded like another useful avenue, but it turns out that I had done that already :( –  glenatron Jul 13 '09 at 9:06
add comment

Well, I think for the user@company.com you'll need to add the attribute attributeMapUsername to the provider string. Typically I use "userPrincipleName" for user@company.com and "sAMAccountName" for "domain\user" setups. At least I think that's the relationship, but I don't have the code handy to double check. There could be other reasonable settings for related scenarios, but I'm not certain what they'd be.

share|improve this answer
add comment

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.