[Bug]: Cannot configure LDAP if the user and password are empty (anonymous access to LDAP)

[krzotr]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

In v33 I want to configure LDAP integration. My LDAP has anonymous access, so I do not need to put the User DN / Password.

In the LDAP configuration i put the host, port, and base DN, and click "Test connection" I see an error.

Invalid configuration: Mandatory field "LDAP Login Filter" left empty

I try to click on Ldap Attributes tab, but it is not active. I see a description of User DN - The DN of the client user with which the bind shall be done. For anonymous access, leave DN and Password empty. - should work.

I tested it on Nextcloud 31 everything was working as expected

I see the source code of LDAPSettingsApp.vue file https://github.com/nextcloud/server/blob/v33.0.0/apps/user_ldap/src/views/LDAPSettingsApp.vue#L123 . Condition is wrong because to get access to all tabs i also need to fill user dn and password, so it is not possible to configure anonymously.

Steps to reproduce

1. Go to Administration Settings
2. Go to LDAP/AD integration
3. Fill Host, port, and Base DN (do not fill User DN and Password)
4. Click "Test Connection."
5. Error Invalid configuration: Mandatory field "LDAP Login Filter" left empty
6. Ldap Attributes tab is inactive, so I cannot fill LDAP login filter
7. Fill User DN and Password and click Save credentials
8. Users, Log Attributes, Groups etc. tabs are available
9. Remove User DN and Password
10. Save Credentials
11. Users, Log Attributes, Groups etc. tabs are not available
12. Cannot configure LDAP without putting user DN and password

ldap.mp4

Expected behavior

I should configure LDAP without putting the user DN and password; it was working in version 31

Nextcloud Server version

33

Operating system

RHEL/CentOS

PHP engine version

PHP 8.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

{
    "system": {
        "htaccess.RewriteBase": "\/",
        "memcache.local": "\\OC\\Memcache\\APCu",
        "apps_paths": [
            {
                "path": "\/var\/www\/html\/apps",
                "url": "\/apps",
                "writable": false
            },
            {
                "path": "\/var\/www\/html\/custom_apps",
                "url": "\/custom_apps",
                "writable": true
            }
        ],
        "upgrade.disable-web": true,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "nextcloud.devel"
        ],
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "mysql",
        "version": "33.0.0.16",
        "overwrite.cli.url": "http:\/\/nextcloud.devel",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbtableprefix": "oc_",
        "mysql.utf8mb4": true,
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory"
    }
}

List of activated Apps

Enabled:
  - activity: 6.0.0-dev.0
  - app_api: 33.0.0
  - bruteforcesettings: 6.0.0-dev.0
  - calendar: 6.2.1
  - circles: 33.0.0
  - cloud_federation_api: 1.17.0
  - comments: 1.23.0
  - contacts: 8.4.2
  - contactsinteraction: 1.14.1
  - dashboard: 7.13.0
  - dav: 1.36.0
  - federatedfilesharing: 1.23.0
  - federation: 1.23.0
  - files: 2.5.0
  - files_downloadlimit: 5.1.0-dev.0
  - files_pdfviewer: 6.0.0-dev.0
  - files_reminders: 1.6.0
  - files_sharing: 1.25.2
  - files_trashbin: 1.23.0
  - files_versions: 1.26.0
  - firstrunwizard: 6.0.0-dev.0
  - logreader: 6.0.0
  - lookup_server_connector: 1.21.0
  - mail: 5.7.5
  - nextcloud_announcements: 5.0.0
  - notes: 4.13.1
  - notifications: 6.0.0
  - oauth2: 1.21.0
  - password_policy: 5.0.0-dev.0
  - photos: 6.0.0-dev.0
  - privacy: 5.0.0-dev.0
  - profile: 1.2.0
  - provisioning_api: 1.23.0
  - recommendations: 6.0.0-dev.0
  - related_resources: 4.0.0-dev.0
  - richdocuments: 10.1.2
  - richdocumentscode: 25.4.904
  - serverinfo: 5.0.0-dev.0
  - settings: 1.16.0
  - sharebymail: 1.23.0
  - spreed: 23.0.2
  - support: 5.0.0
  - survey_client: 5.0.0-dev.0
  - systemtags: 1.23.0
  - text: 7.0.0-dev.3
  - theming: 2.8.0
  - twofactor_backupcodes: 1.22.0
  - twofactor_totp: 15.0.0-dev.0
  - updatenotification: 1.23.0
  - user_ldap: 1.24.0
  - user_status: 1.13.0
  - viewer: 6.0.0-dev.0
  - weather_status: 1.13.0
  - webhook_listeners: 1.5.0
  - workflowengine: 2.15.0
Disabled:
  - admin_audit: 1.23.0
  - encryption: 2.21.0
  - files_external: 1.25.1
  - suspicious_login: 11.0.0-dev.0
  - twofactor_nextcloud_notification: 7.0.0

Nextcloud Signing status

No errors have been found.

Nextcloud Logs

Additional info

Tested on No errors have been found.

[Salicath]

I had the same error and fixed it by editing the LDAP Query and inserting this: (&(objectclass=person)(sAMAccountName=%uid))

[szaimen]

cc @nextcloud/idp