Skip to content

Latest commit

 

History

History
48 lines (42 loc) · 3.72 KB

CHANGELOG.md

File metadata and controls

48 lines (42 loc) · 3.72 KB
Raw

Change log for LDAPCP

Unreleased

  • Add more strict checks on the claim type passed during augmentation and validation, to record a more meaningful error if needed
  • Add test to ensure that LDAPCP augments only entities issued from the TrustedProvider it is associated with
  • Fix sign-in of users failing if LDAPCP configuration does not exist
  • Handle potential exception during augmentation if connection to LDAP server fails
  • Improve managemend of special LDAP characters
  • Add property CustomData to ILDAPCPConfiguration
  • Fix msbuild warnings
  • Improve tests
  • Use Azure DevOps to build LDAPCP
  • Cache result returned by FileVersionInfo.GetVersionInfo() to avoid potential hangs
  • Add property AzureCPConfig.MaxSearchResultsCount to set max number of results returned to SharePoint during a search
  • Cache domain name and domain FQDN of each LDAP Connection, to avoid repetitive and potentially slow queries to LDAP servers
  • Deprecate method LDAPCP.SetLDAPConnection called each time a LDAP operation is about to occur. Instead, added a separate method LDAPCP.SetLDAPConnection, called only during initialization of the configuration. Domain name, domain FQDN and distinguishedName are retrieved and cached here.
  • Improve global performance by caching domain name and domain FQDN of each LDAP Connection, to avoid repetitive and potentially slow queries to LDAP servers
  • Update logging during augmentation, and split various LDAP operations into different SPMonitoredScope
  • Update augmentatikon by getting, using and caching RootContainer for each DirectoryEntry object
  • Do more fine-grained test when excluding a LDAP user missing the identity attribute
  • Update NuGet package NUnit to v3.11
  • Update NuGet package NUnit3TestAdapter to v3.13
  • Update NuGet package CsvTools to v1.0.12

LDAPCP v11 enhancements & bug-fixes - Published in August 30, 2018

  • Fixed no result returned under high load, caused by a thread safety issue where the same filter was used in all threads regardless of the actual input
  • Fixed the augmentation that randomly failed under high load, caused by a thread safety issue on list ILDAPCPConfiguration.LDAPConnectionsProp
  • Added handling of special characters for LDAP filters as documented in https://ldap.com/ldap-filters/
  • Added the first nae (givenName) in the list of attributes queried by default
  • Improved validation of changes made to ClaimTypes collection
  • Added method ClaimTypeConfigCollection.GetByClaimType()
  • Implemented unit tests
  • Explicitely encode HTML messages shown in admin pages and renderred from server side code to comply with tools scanning code to detect security vulnerabilities
  • Deactivating farm-scoped feature "LDAPCP" removes the claims provider from the farm, but it does not delete its configuration anymore. Configuration is now deleted when feature is uninstalled (typically when retracting the solution)
  • Added user identifier properties in global configuration page

LDAPCP v10 enhancements & bug-fixes - Published in June 12, 2018

  • LDAPCP can be entirely configured with PowerShell, including claim types configuration
  • LDAPCP administration pages were updated to be easier to udnerstand, especially the page that configures claim types.
  • LDAPCP administration pages can now be easily reused by developers.
  • Augmentation can now handle multiple group claim types, and uses the credentials set when LDAP connection was added.
  • Number of results returned by LDAP servers is now limited to improve performance of LDAP servers.
  • Logging is more relevant and generates less messages.
  • Beaking change: Due to the amount of changes in this area, the claim types configuration will be reset if you update from an earlier version.
  • Many bug fixes and optimizations