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
When entering a malformed LDAP-Search Query (configuration variable: user_ldap / ldap_userlist_filter), your instance of NC will instantly crash (http-requests not finishing/timeouting, even for the frontpage), because settings are instantly saved, or at least when you hit the "test settings" button.
Actual behaviour
Let's say you want your users pick from those who have "posixAccount" (or mailAddress or whatever), and are member of the group people to avoid "virtual" accounts, your query might look like this: (|(objectclass=posixAccount)(&(memberOf=ou=people)))
this works fine, everything's okay. Assume that in your User-List are some unwanted entries, which you want to get rid of, and you might want to exclude groups instead or additionally, e.g. by replacing the & with an !. This will of course not work, but it will instantly kill your NC-Instance. (|(objectclass=posixAccount)(&(memberOf=ou=people)(!(memberOf=ou=virtual))))
Expected behaviour
Popup showing information, that you've entered a Malformed search-query and do not test, until it is at least syntactically correct.
Quick Fix:
If you - like me - accidentally ran into that problem, you can try disabling the ldap-plugin, set a correct value by hand, and reactivate the plugin. If needed, restart the Webserver and/or the DB:
Updated from an older Nextcloud/ownCloud or fresh install: fresh install
fresh
this seems not to be a big deal, but it is quite annoying, that a simple typo can instantly crash your setup, and it is at least some lost time in researching what went wrong, even if the administrator is capable to fix this rather quickly. Imho a sanity check would make sense here.
The text was updated successfully, but these errors were encountered:
I am going to close this since there doesn't seem to be a lot of interest (no upvotes) and no respond since around 2 years.
If this is still happening please make sure to upgrade to the latest version. After that, feel free to reopen.
When entering a malformed LDAP-Search Query (configuration variable: user_ldap / ldap_userlist_filter), your instance of NC will instantly crash (http-requests not finishing/timeouting, even for the frontpage), because settings are instantly saved, or at least when you hit the "test settings" button.
Actual behaviour
Let's say you want your users pick from those who have "posixAccount" (or mailAddress or whatever), and are member of the group people to avoid "virtual" accounts, your query might look like this:
(|(objectclass=posixAccount)(&(memberOf=ou=people)))
this works fine, everything's okay. Assume that in your User-List are some unwanted entries, which you want to get rid of, and you might want to exclude groups instead or additionally, e.g. by replacing the & with an !. This will of course not work, but it will instantly kill your NC-Instance.
(|(objectclass=posixAccount)(&(memberOf=ou=people)(!(memberOf=ou=virtual))))
Expected behaviour
Popup showing information, that you've entered a Malformed search-query and do not test, until it is at least syntactically correct.
Quick Fix:
If you - like me - accidentally ran into that problem, you can try disabling the ldap-plugin, set a correct value by hand, and reactivate the plugin. If needed, restart the Webserver and/or the DB:
Nextcloud version:
10.0
Updated from an older Nextcloud/ownCloud or fresh install: fresh install
fresh
this seems not to be a big deal, but it is quite annoying, that a simple typo can instantly crash your setup, and it is at least some lost time in researching what went wrong, even if the administrator is capable to fix this rather quickly. Imho a sanity check would make sense here.
The text was updated successfully, but these errors were encountered: