LDAP Authentication Issue: QNAP Active Directory - "Invalid username or password"

[kayzer699 1]

Hello Emby Community,

I am having trouble configuring the LDAP plugin on my QNAP NAS using the built-in Active Directory (Domain Controller). Despite various configuration attempts, I consistently receive the "Invalid username or password" error in Emby.

Environment:

• Server: QNAP NAS (QTS 5.x)

• LDAP Source: QNAP Active Directory Controller

• User Status: The user (asli) can successfully log in to the QNAP Web UI. Application permissions (Desktop/File Station) are granted.

Current LDAP Plugin Settings in Emby:

• LDAP Server Address: 127.0.0.1 (Also tried local IP)

• Port: 389

• Bind DN: cn=administrator,cn=Users,dc=koken,dc=home

• Bind Credentials: (Verified admin password)

• User Search Base: dc=koken,dc=home

• User Search Filter: (sAMAccountName={0}) (Also tried (&(CN={0})))

The Issue: When I attempt to log in with the username asli, Emby returns an authentication error. I have tried logging in as asli and KOKEN\asli, but neither works.

The user exists in the cn=Users container on the QNAP Domain Controller. I have already enabled "Allow LDAP authentication" in the Emby User settings.

What could be missing in my DN syntax or search filter for a QNAP-based AD setup?

Any help would be appreciated.

[Luke 42100]

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[kayzer699 1]

Thank you for help.

embyserver-63907701201.txt embyserver-63907701919.txt embyserver-63907731883.txt embyserver-63907747199.txt hardware_detection-63907701266.txt hardware_detection-63907701983.txt embyserver-63907701620.txt hardware_detection-63907701685.txt hardware_detection-63907731949.txt embyserver.txt

[Luke 42100]

The error message in the log is saying Strong authentication required. Here is some info that I found:

Quote

The "Strong(er) authentication required" (LDAP error message occurs when an LDAP client attempts an insecure bind or operation (usually plain LDAP on port 389) against an Active Directory server enforcing LDAP signing or TLS/SSL (LDAPS). Fix this by switching to LDAPS (port 636) or configuring the client for TLS, rather than disabling security on the server.

Please let us know if this helps. Thanks.