- Fix error when creating the configuration if the trust uses an identifier claim type that is not well-known by LDAPCP - #221
- Improve tests, to make them much easier to replay from a new test environment, and with many more users and groups
- Fix error when creating the configuration, due to case-sensitive test in the claim types - #204
- Fix the error when loading the global configuration page, if the group claim type set in the LDAPCP configuration does not exist in the trust - #203
- Add the property MaxSearchResultsCount, to override the SharePoint limit of the maximum number of objects that the LDAP server returns - #209
- Correctly initialize LDAP-specific properties with their actual value, instead of the default value of the type - #212
- Fix an NullReferenceException in a very rare scenario where ClaimsPrincipal.Identity is null
- Add helper methods to get/delete a directory connection in the configuration
- Ignore case when comparing claim types, to avoid errors when creating the configuration - #205
- IMPORTANT: due to the move to GitHub Actions and the configuration of the builtin Windows VM, LDAPCP now requires at least .NET 4.6.2
- CI/CD is now implemented using GitHub Actions instead of Azure DevOps
- Fix: During augmentation, connection to LDAP always used SimpleBind, regardless of the authentication settings
- Fix: "Apply to all user attributes" now only updates user entities (not also groups)
- Reference SharePoint assemblies locally instead of the GAC
- Augmentation is now enabled by default on a new LDAP connection, when it is added through the UI
- Augment groups with the same attribute as the one set in the LDAPCP configuration. #148
- Fix: In claims configurfation page, the values in the list of "PickerEntity metadata" was not populated correctly, which caused an issue with the "Title" (and a few others)
- Update NuGet package NUnit3TestAdapter to v3.16.1
- Update NuGet package Newtonsoft.Json to 12.0.3
- Fix regression: after installing v14, users are stuck in SharePoint just after sign-in to ADFS. #99
- Add method LDAPCPConfig.CreateDefaultConfiguration
- Fix bug: randomly, LDAPCP returned results that were missing their domain name. In SharePoint logs, a DirectoryServicesCOMException error was recorded. #87
- Add a default mapping to populate the email of groups
- Update text in claims mapping page to better explain settings
- Fix bug: During augmentation, PrincipalContext is not built with expected ContextOptions if LDAPConnection.UseSPServerConnectionToAD is true
- Improve logging during augmentation
- Improve logging when testing augmentation doesn't return expected result
- Update DevOps build pipelines
- Improve code quality as per Codacy's static code analysis
- Update NuGet package NUnit from 3.11 to 3.12
- Make most of public members privates and replace them with public properties, to meet best practices
- Use reflection to copy configuration objects, whenever possible, to avoid misses when new properties are added
- 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
- 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 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