This project has moved. For the latest updates, please go here.

LDAP attribute

Oct 18, 2013 at 10:36 PM
Edited Oct 18, 2013 at 10:43 PM
Hi

I experience a wierd problem with the claimsprovider for SharePoint 2013. I connect against a SUN LDAP directory and the connection works fine. I´m trying to map http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname and it works for many LDAP attributes sn, id, cn etc but for som reason when i try my identifier attribute i get no results back.

In ULS log i get: [LDAPCP] Got 1 results with query "(|(&(objectclass=person) (xxxxxxxxxxxid=anders1*)))" a5f94d9c-60fe-30e0-d391-8af850b8d355

So something must happen in the parsing of the result. If i change xxxxxxxxxxxid to for example cn or ou everything works. Can it be the length of the attribute?

We are using the 2010 version in our 2010 farms and it works there with the same attribute connected to the same directory.

Best regards
Anders
Coordinator
Oct 21, 2013 at 12:29 PM
hello Anders,
are you using the standard version or did you customize LDAPCP by inheriting the class?
There should be no difference between 2010 and 2013 version, both are 99% similar, especially in the processing of the results.
Can you validate that the claim type mapping list is the same between LDAPCP 2010 and 2013?
If you use the standard version, you can find it in central admin > security > Claims mapping
cheers,
Yvan
Oct 21, 2013 at 12:36 PM
Hi

In using the standard version. Not developer version.

I have verified the list. And tried with only the Login claim.

Any other ideas?

Anders
Coordinator
Oct 21, 2013 at 12:40 PM
hello,
does it work if you use only the LDAP attribute xxxxxxxxxxxid in the claims list (mapped to Login claim)?
cheers,
Yvan
Oct 21, 2013 at 12:40 PM
The attributes we are trying to read is ingerited from a custom object Class?

Could that be a problem in 2013 version?

Anders
Oct 21, 2013 at 12:43 PM
In using only the Login claim. One row. But i dosn't work with the xxxxxx.. attribute.
It works with cm, manager and the basic attributes.

Best regards
Anders
Coordinator
Oct 21, 2013 at 12:47 PM
just to be on the safe side, can you try on a new site collection?
sometimes SharePoint behaves strangely on existing site collections...