-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ldap] Add ldap domain socket (ldapi:///) support #24497
Comments
Thanks @zenlord. |
I'm struggling with the frontend patch. I have made the required changes to get the Wizard to respond 'Configuration OK', but the tab headings for 'Users', 'Login Attributes' etc. stay greyed out and do not become available. @nextcloud/ldap @blizzz any hints where the checks to enable these tabs can be found so I can send in a pull request? |
@zenlord this probably depends on ajax/testConfiguration.php which eventually triggers the |
@blizzz At first I thought my configuration was at fault, but even after resetting to default I still was unable to switch tabs in the LDAP settings section. The ajax/ folder doesn't contain anything relevant, but the js/wizard/ folder does (83 hits for 'port' spread over 20 files :( ), and it seems that quite some checks are triggering an auto-detection of the port number. I'll do some further digging, but JS is not my strongsuit. |
I made some progress by adding an additional condition in two functions inside js/wizard/view.js: basicStatusCheck()
(and similar in functionalityCheck() But the behaviour is erratic: e.g. the check for a username returns 'user found', but the count for users returns 0 ... |
Errors were indeed in my configuration (and in me misunderstanding the 'edit Query filter' functionality - one has to click the underlined text for the filter in the textfield to become active...). |
Not sure what I have to do. I have filed a pull request that solves this issue almost one year ago, and I am able to apply the patches manually to versions 20, 21 and now also 22.2.3. The PR just sits there. |
Yes, I just upgraded this instance to v26.0.3 and I no longer have to patch the source files myself. |
See ##7737 for a description of the issue. That bug was closed in May 2019, but in my 20.0.2 installation of nextcloud, the problem is still present.
I have identified the files that require changes in the user_ldap app:
Making the changes to the backend files as done previously by @nick-dumas in his commit nick-dumas@72b8054 has proven to work for me, so I intend to make the required changes and then send in a PR.
The text was updated successfully, but these errors were encountered: