This release is deprecated and is not updated anymore.
instead.Changes in v18.104.22.168 (published 09/11/2012)
Documentation to comeChanges in v22.214.171.124 (published 19/10/2012)
- Added property DisplayMeInsteadOfIdentityValueInEntityDisplayText to offer new customization capability:
Identity claim type may use an attribute where its value doesn't mean anything to users (for example a corporate ID). In that case, set this property to use another LDAP attrbute to display the permission so that user permissions list is more readable. Check "LDAPCP 2010 for Developers" to see how to implement
- Added a SPMonitoredScope to monitor waiting time to get retults of LDAP request from serverChanges in v126.96.36.199 (published 09/10/2012)
- Changed behavior: now 2 values with different case (for ex. "value" and "Value") are considered as identical, since SharePoint itself seems to always pass values in lowercase to FillResolve method
- Added property IgnoreCaseToDetectDuplicatesValues to override behavior above and revert to previous behavior
- Changed method name InitLDAPConnection to SetLDAPConnection
- Changed property name AlwaysResolveAgainstIdentityClaim to ResolveAsIdentityClaim
- Changed scope of some properties in AttributeHelper class to be available in classes that inherit LDAPCP
- Updated sample classes in package for developerChanges in v188.8.131.52 (published 17/09/2012)
- Code refactoring to support connection to multiple LDAP / AD
- Updated LDAPCP for Developers to add a sample to connect to multiple LDAP
- Handle scenario where identity claim is missing in the list of LDAP attributes to queryChanges in v184.108.40.206
- Fixed: memory leak issueChanges in v220.127.116.11
- Fixed: people picker throws an error in central admin when creating a new site collection in a web application that does not contain a root site collectionChanges in v2.0
Major code refactoring that brings many improvements in terms of performance and reliability:
- New: Performs only 1 LDAP query per search, which makes claim provider performing signigicantly faster when there are many claim types defined in a trust, or when LDAP is slow to respond
- New: Always search input against common attributes such as the display name and common name (even if not defined in the trust)
- Change: Preserves the original name of the trust in the people picker, instead of showing "LDAPClaimProvider"
- Change: Preserves the original display name of the claims in the hierarchyChanges in v1.1
- New: It now provides the administrator with a configuration page to set the LDAP directory to use. It is accessible in Central Admin > Security, under General Security section.
- Change: the logging to ULS has been reviewed to be more accurateChanges in v1.0
- New: Supports inheritance to easily create claim provider that inherits from this one. The goal is to very easily connect to a different LDAP or to customize its default behavior such as the attributes list or messages in the people picker. The source code contains a separate project to illustrate how to do it.
- New: Write events in SharePoint logs, in a category called "LDAP Claim Provider"
- Fixed: the claim provider cannot be used anymore in web applications where the trust is not activated
- A lot of optimizations in the code
- Fixed minor bugs