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 have a claims auth site setup right now with both Windows & Forms. Providers are configured for LDAP auth. This works without an issue. I want users to be able to sign in to SharePoint using their username, aka, sAMAccountName. This also works, but I want to see the users display name in the upper corner of SharePoint while they are signed in. Here's my provider:

<add name="ldapMembership"
      type="Microsoft.Office.Server.Security.LdapMembershipProvider, Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
      server="cncydev.cncy.com"
      port="389"
      useSSL="false"
      userDNAttribute="distinguishedName"
      userNameAttribute="sAMAccountName"
      userContainer="CN=Users,DC=cncy,DC=com"
      userObjectClass="person"
      userFilter="(ObjectClass=person)"
      scope="Subtree"
      otherRequiredUserAttributes="sn,givenname,cn,mail,distinguishedName" />

My impression is that the userDNAttribute controls the display name of what shows in SharePoint, but this property never seems to make a difference. I've also seen useDNAttribute="true", but that doesn't get respected either. For the property I want to display, does it need to be mapped to a SharePoint user profile property?

share|improve this question
    
Is this Active Directory you're authenticating against, or another Directory Service? –  Trevor Seward May 25 '12 at 20:54
    
Yes, Active Directory –  Tim Gabrhel May 26 '12 at 12:28
add comment

2 Answers

You need to set up the UPA to sync to AD, as you're aware. On that Sync connection, you need to map the SPS-ClaimID to sAMAccountName.

share|improve this answer
    
Could you clarify a bit further? I'm able to authenticate against the sAMAccountName. How does mapping that to the SPS-ClaimID fix my user name issue? –  Tim Gabrhel May 29 '12 at 15:12
    
It tells the UPA that the sAMAccountName (or whatever attrib your users might use as a login attribute) maps to the ClaimID. This is how you "tell" the UPA to match user logins with UPA profiles. –  Trevor Seward May 29 '12 at 17:36
    
Do you have any references? I have the property mapped but I feel as if there are some steps missing on my end. –  Tim Gabrhel May 30 '12 at 14:51
    
I've created my AD Sync Connection to use my Ldap Membership provider, I've synced profiles over, mapped the SPS-ClaimID to the sAMAccountName and that all works fine. So what am I missing to get 'Timothy Gabrhel' to show up in SharePoint rather than 'tgabrhel'? I sign in with tgabrhel and that's all that shows. I do not want to have to update the DisplayName. –  Tim Gabrhel Jun 1 '12 at 18:16
add comment

You may be looking at the following - though they are implementing FBA which I am not sure you are. Here is the resource: link (msdn forums).

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.