K2 Trusted LDAP User Manager
When using K2 Trusted LDAP User Manager with LDAP servers that comply with LDAP v3 but aren't Windows-based, you might encounter a specific issue with the "manager" attribute: User searches can fail: If the "manager" attribute isn't mapped correctly or doesn't exist on the LDAP server, user searches might unexpectedly fail. This behavior is different from other non-mapped or non-existent attributes, which typically don't cause search failures. To address this issue, follow these steps: Check for a matching attribute: Verify if the LDAP server has an attribute that corresponds to the "manager" attribute in K2. Map the attribute correctly: If a matching attribute exists, ensure it's mapped accurately in the K2 configuration. Here's an example of a correct mapping: XML < K2LdapMapping K2Name = "Manager" FullOnly = "true" LdapName = "manager" ObjectType = "System.String" SearchQuery = ...