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:

  1. Check for a matching attribute: Verify if the LDAP server has an attribute that corresponds to the "manager" attribute in K2.

  2. 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="(&amp;(objectClass=Person)(objectCategory=User))" SearchResultProperty="samAccountName" />
  3. Remove the mapping if necessary: If the LDAP server doesn't have a matching attribute, remove the "manager" mapping from the K2 configuration. This prevents the "object does not exist" error from occurring.

By following these steps, you can ensure that user searches function as expected when using K2 Trusted LDAP User Manager with non-Windows LDAP v3 compliant servers.

Comments

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7