LDAP extension Error

[dylan62370 6]

Hello,

I currently have a Windows server that runs an Active Directory (AD).

All my Linux services (Gitlab, Grafana, etc...) are connected to my AD. It works perfectly, but I can't connect my Emby to it.

I installed the LDAP extension and configured everything and when I choose the user it says "Incorrect username or password. Try again."

It doesn't even load in 2 seconds it shows this is if I change the IP it's the same.... However if I ping the LDAP no problem it pings so it reaches the LDAP.

 

[Luke 38850]

Hi, what do you mean "doesn't even load in 2 seconds"? Please attach the emby server log from when the problem was experienced:

How to Report a Problem

Thanks.

[dylan62370 6]

Hello @Luke

When I say "doesn't even load in 2 seconds" it's because when I type my username and password of my user present in the AD and I click on connect I have the impression that it's not even going to search in the AD it displays the error 2 seconds later.

I forgot to specify some point.
The Emby server runs on Linux Debian 10.

 

Here is the information I found in the logs

Here is the log file embyserver.txt

2023-04-12 22:01:24.881 Info Server: http/1.0 POST http://‌‍‍127.0.0.1‌:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby%20Web&X-Emby-Device-Name=Firefox%20macOS&X-Emby-Device-Id=10a7204b-23b5-4a3a-907d-d823e8e32162&X-Emby-Client-Version=4.7.11.0&X-Emby-Language=fr. Accept=application/json, Connection=close, Host=127.0.0.1:8096, User-Agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0, Accept-Encoding=gzip, deflate, br, Accept-Language=fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3, Content-Type=application/x-www-form-urlencoded; charset=UTF-8, Origin=https://emby.dylan-pacques.fr, Referer=https://emby.dylan-pacques.fr/web/index.html, Content-Length=39, DNT=1, Sec-Fetch-Dest=empty, Sec-Fetch-Mode=cors, Sec-Fetch-Site=same-origin
2023-04-12 22:01:25.135 Error UserManager: Error authenticating with provider LDAP
        *** Error Report ***
        Version: 4.7.11.0
        Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
        Operating system: Linux version 4.19.0-22-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.260-1 (2022-09-29)
        Framework: .NET 6.0.8
        OS/Process: x64/x64
        Runtime: opt/emby-server/system/System.Private.CoreLib.dll
        Processor count: 12
        Data path: /var/lib/emby
        Application path: /opt/emby-server/system
        Novell.Directory.Ldap.LdapLocalException: LdapLocalException: Invalid comparison operator (87) Filter Error
        Source: LDAP
        TargetSite: Int32 get_FilterType()

2023-04-12 22:01:25.143 Info HttpClient: POST https://connect.emby.media/service/user/authenticate
2023-04-12 22:01:25.559 Info UserManager: Authentication request for dylanp has been denied.
2023-04-12 22:01:25.578 Warn Server: AUTH-ERROR: 127.0.0.1 - Invalid username or password entered.
2023-04-12 22:01:25.578 Error Server: Invalid username or password entered.
2023-04-12 22:01:25.582 Info Server: http/1.0 Response 401 to ‌‍‍127.0.0.1‌. Time: 698ms. http://‌‍‍127.0.0.1‌:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby%20Web&X-Emby-Device-Name=Firefox%20macOS&X-Emby-Device-Id=10a7204b-23b5-4a3a-907d-d823e8e32162&X-Emby-Client-Version=4.7.11.0&X-Emby-Language=fr

 

[Luke 38850]

what did you configure for your ldap search filter? the error would suggest. The error would suggest you've specified something invalid, either for that option, or one of the others.

So that's why the login attempt never even hits your ldap server.

[dylan62370 6]

I have configured this option (see screenshot)

I have the same thing on other LDAP clients

[Luke 38850]

Are you not able to leave it at default?

[dylan62370 6]

Hello @Luke

I have the same problem using the example.

I also specify I use the AD of my active directory present on my Windows Server 2019

I added in capture what I put exactly.

This is log:

2023-04-14 12:24:24.680 Info HttpClient: POST https://mb3admin.com/admin/service/registration/validate
2023-04-14 12:24:25.302 Error UserManager: Error authenticating with provider LDAP
        *** Error Report ***
        Version: 4.7.11.0
        Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb
        Operating system: Linux version 4.19.0-22-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.260-1 (2022-09-29)
        Framework: .NET 6.0.8
        OS/Process: x64/x64
        Runtime: opt/emby-server/system/System.Private.CoreLib.dll
        Processor count: 12
        Data path: /var/lib/emby
        Application path: /opt/emby-server/system
        Novell.Directory.Ldap.LdapException: LdapException: Operations Error (1) Operations Error
        LdapException: Server Message: 000004DC: LdapErr: DSID-0C090A5E, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v4563
        LdapException: Matched DN:
        Source: LDAP
        TargetSite: Void ChkResultCode()

2023-04-14 12:24:25.304 Info HttpClient: POST https://connect.emby.media/service/user/authenticate
2023-04-14 12:24:25.841 Info UserManager: Authentication request for dylanp has been denied.
2023-04-14 12:24:25.847 Warn Server: AUTH-ERROR: 127.0.0.1 - Invalid username or password entered.
2023-04-14 12:24:25.847 Error Server: Invalid username or password entered.
2023-04-14 12:24:25.847 Info Server: http/1.0 Response 401 to ‌‍‍127.0.0.1‌. Time: 1271ms. http://‌‍‍127.0.0.1‌:8096/emby/Users/authenticatebyname?X-Emby-Client=Emby%20Web&X-Emby-Device-Name=Firefox%20macOS&X-Emby-Device-Id=9af8a14c-da42-419d-8634-3cd5d225f3b7&X-Emby-Client-Version=4.7.11.0&X-Emby-Language=fr

 

Edited April 14, 2023 by dylan62370

[Luke 38850]

Can you try using an exact copy of that example text from underneath the field and see how that compares?

[dylan62370 6]

Hello @Luke

I tested "uid={0}" and "(uid={0})" same error.

[Luke 38850]

OK I'm afraid I'm not sure of the issue as those defaults typically work well for most setups.

[dylan62370 6]

Maybe he doesn't like that it's an active directory running on Windows Server

[amateurgod 29]

what IP do you have the LDAP plugin pointed to for the AD server as the logs show 127.0.0.1 which would be localhost (The machine emby is running on) however im not to familiar with LDAP plugin for emby and if that 127.0.0.1 is emby talking to itself rather than the AD server

[dylan62370 6]

Hello @amateurgod

I don't understand why it points to the localhost but the ip of the Emby is 10.0.0.26
I don't know where I can change the IP of the plugin. Because I have indicated in the LDAP plugin the IP of my AD (see picture)

[amateurgod 29]

do you have any firewalls or anything that could be blocking outgoing ports on your emby server?

[dylan62370 6]

50 minutes ago, amateurgod said:

do you have any firewalls or anything that could be blocking outgoing ports on your emby server?

I have no firewall on my local network, especially since the Emby server and the AD server are on the same network and no firewall between them. I have the Windows Server firewall on the AD but it doesn't block for my other clients so it must not block for Emby.