You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation for LDAP integration requires that LDAP directory search is only one level deep. This means that developers seeking to integrate their directories with LDAP must ensure that all users seeking to login into the system must be grouped under one Base DN. This is not realistic for organizations with complex established directory structures. It might not be realistic for all users to be grouped under one base DN. Therefore, with the current implementation in which sub tree search is defaulted to one level, LDAP integration will fail. I'm therefore, proposing that one more property be added to applications properties file in the section under LDAP settings for instance auth.ldap.user.search.sub.tree = true. The appropriate code modifications are then made in the AvailableAppSettings Interface the AxelorLdapProfileService class to accommodate this property. This will ensure that users with complex directory structures can now integrate their directories with Axelor. I have done this in my project and thought it will be great to have it included as part of standard code
The text was updated successfully, but these errors were encountered:
jinkoom
changed the title
[6.1.5] LDAP Integration Not Working
[6.1.5] LDAP Integration Not Working In some Cases
Feb 25, 2024
The current implementation for LDAP integration requires that LDAP directory search is only one level deep. This means that developers seeking to integrate their directories with LDAP must ensure that all users seeking to login into the system must be grouped under one Base DN. This is not realistic for organizations with complex established directory structures. It might not be realistic for all users to be grouped under one base DN. Therefore, with the current implementation in which sub tree search is defaulted to one level, LDAP integration will fail. I'm therefore, proposing that one more property be added to applications properties file in the section under LDAP settings for instance auth.ldap.user.search.sub.tree = true. The appropriate code modifications are then made in the AvailableAppSettings Interface the AxelorLdapProfileService class to accommodate this property. This will ensure that users with complex directory structures can now integrate their directories with Axelor. I have done this in my project and thought it will be great to have it included as part of standard code
The text was updated successfully, but these errors were encountered: