[GH-ISSUE #364] How to setup a connection? #137

Closed
opened 2026-02-27 08:15:27 +03:00 by kerem · 5 comments
Owner

Originally created by @SaschMie on GitHub (Nov 3, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/364

hello all,

i have lldap installed on my unraid nas and i am currently trying to understand how an application can access it.

The dn is set to dc=example,dc=org.

Now I am trying to connect emby to it, however I am not clear what settings it needs now.

image

The log of lldap shows me that the connection works.

2022-11-03T09:01:25.642002244+00:00 INFO     LDAP session [ 115µs | 61.14% / 100.00% ]
2022-11-03T09:01:25.648153101+00:00 INFO     ┕━ LDAP request [ 44.7µs | 38.86% ]

But i cant login with a tester user, emby claims all time that the credentials are wrong.

Maybe someone can help here?

Originally created by @SaschMie on GitHub (Nov 3, 2022). Original GitHub issue: https://github.com/lldap/lldap/issues/364 hello all, i have lldap installed on my unraid nas and i am currently trying to understand how an application can access it. The dn is set to dc=example,dc=org. Now I am trying to connect emby to it, however I am not clear what settings it needs now. <img width="768" alt="image" src="https://user-images.githubusercontent.com/101413773/199682932-e1fd5312-0fe3-4679-a478-dde487aab8ae.png"> The log of lldap shows me that the connection works. ``` 2022-11-03T09:01:25.642002244+00:00 INFO LDAP session [ 115µs | 61.14% / 100.00% ] 2022-11-03T09:01:25.648153101+00:00 INFO ┕━ LDAP request [ 44.7µs | 38.86% ] ``` But i cant login with a tester user, emby claims all time that the credentials are wrong. Maybe someone can help here?
kerem closed this issue 2026-02-27 08:15:27 +03:00
Author
Owner

@martadinata666 commented on GitHub (Nov 3, 2022):

https://github.com/nitnelave/lldap/blob/main/example_configs/emby.md

<!-- gh-comment-id:1301830641 --> @martadinata666 commented on GitHub (Nov 3, 2022): https://github.com/nitnelave/lldap/blob/main/example_configs/emby.md
Author
Owner

@nitnelave commented on GitHub (Nov 3, 2022):

Have you had a look at the provided example_configs?

A little LDAP vocabulary: DN is distinguished name, the full identifier for
a user or group. The bind DN is the admin user name, and the credentials is
the password.

The user search base is where you have users stored, so "ou=people,
DC=example, DC=com".
The user filter is how to find a user trying to log in, so you can have
(uid={0}) for the basic login, or you can make it so they can log in with
email as well, or restrict them to a specific group.

What application is that config for? Once you get it working, I'd
appreciate if you could contribute your configuration for the next person.

On Thu, 3 Nov 2022, 10:10 Sascha, @.***> wrote:

hello all,

i have lldap installed on my unraid nas and i am currently trying to
understand how an application can access it.

The dn is set to dc=example,dc=org.

Now I am trying to connect emby to it, however I am not clear what
settings it needs now.

[image: image]
https://user-images.githubusercontent.com/101413773/199682932-e1fd5312-0fe3-4679-a478-dde487aab8ae.png

The log of lldap shows me that the connection works.

2022-11-03T09:01:25.642002244+00:00 INFO LDAP session [ 115µs | 61.14% / 100.00% ]

2022-11-03T09:01:25.648153101+00:00 INFO ┕━ LDAP request [ 44.7µs | 38.86% ]

But i cant login with a tester user, emby claims all time that the
credentials are wrong.

Maybe someone can help here?


Reply to this email directly, view it on GitHub
https://github.com/nitnelave/lldap/issues/364, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGCPWIZBBIXEZSSGIFNULTWGN6Q7ANCNFSM6AAAAAARV5EQSU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

<!-- gh-comment-id:1301834245 --> @nitnelave commented on GitHub (Nov 3, 2022): Have you had a look at the provided example_configs? A little LDAP vocabulary: DN is distinguished name, the full identifier for a user or group. The bind DN is the admin user name, and the credentials is the password. The user search base is where you have users stored, so "ou=people, DC=example, DC=com". The user filter is how to find a user trying to log in, so you can have `(uid={0})` for the basic login, or you can make it so they can log in with email as well, or restrict them to a specific group. What application is that config for? Once you get it working, I'd appreciate if you could contribute your configuration for the next person. On Thu, 3 Nov 2022, 10:10 Sascha, ***@***.***> wrote: > hello all, > > i have lldap installed on my unraid nas and i am currently trying to > understand how an application can access it. > > The dn is set to dc=example,dc=org. > > Now I am trying to connect emby to it, however I am not clear what > settings it needs now. > > [image: image] > <https://user-images.githubusercontent.com/101413773/199682932-e1fd5312-0fe3-4679-a478-dde487aab8ae.png> > > The log of lldap shows me that the connection works. > > 2022-11-03T09:01:25.642002244+00:00 INFO LDAP session [ 115µs | 61.14% / 100.00% ] > > 2022-11-03T09:01:25.648153101+00:00 INFO ┕━ LDAP request [ 44.7µs | 38.86% ] > > > But i cant login with a tester user, emby claims all time that the > credentials are wrong. > > Maybe someone can help here? > > — > Reply to this email directly, view it on GitHub > <https://github.com/nitnelave/lldap/issues/364>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAGCPWIZBBIXEZSSGIFNULTWGN6Q7ANCNFSM6AAAAAARV5EQSU> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
Author
Owner

@SaschMie commented on GitHub (Nov 3, 2022):

It is for emby :)
i tried it not this way (like the example):

image

but im not sure about that bind credentials field, what have to be there. Is that this JWT pw from docker or a pw from an admin user?

Because now i got this:

2022-11-03T09:54:56.560870520+00:00 ERROR       ┝━ 🚨 [error]:  | error: Authentication protocol error for `Protocol error: `This error results from an error during password verification``
2022-11-03T09:54:56.560879214+00:00 ERROR       ┕━ 🚨 [error]:  | error: Authentication error: ` for user 'admin'`

I created a test user named "peter" and he is in the group "emby"

<!-- gh-comment-id:1301870438 --> @SaschMie commented on GitHub (Nov 3, 2022): It is for emby :) i tried it not this way (like the example): ![image](https://user-images.githubusercontent.com/101413773/199692537-8df40e8b-082c-4237-a2cd-cfc123b182c1.png) but im not sure about that bind credentials field, what have to be there. Is that this JWT pw from docker or a pw from an admin user? Because now i got this: ``` 2022-11-03T09:54:56.560870520+00:00 ERROR ┝━ 🚨 [error]: | error: Authentication protocol error for `Protocol error: `This error results from an error during password verification`` 2022-11-03T09:54:56.560879214+00:00 ERROR ┕━ 🚨 [error]: | error: Authentication error: ` for user 'admin'` ``` I created a test user named "peter" and he is in the group "emby"
Author
Owner

@martadinata666 commented on GitHub (Nov 3, 2022):

the sample config said changeme (replace with your password), so replace with your admin password.

<!-- gh-comment-id:1301887920 --> @martadinata666 commented on GitHub (Nov 3, 2022): the sample config said `changeme (replace with your password)`, so replace with your admin password.
Author
Owner

@SaschMie commented on GitHub (Nov 3, 2022):

Yes that was the problem :) now its working! Maybe it should be pointed out in the example that this admin / credentials are an admin of that ldap.

Thank you all :D

<!-- gh-comment-id:1301893173 --> @SaschMie commented on GitHub (Nov 3, 2022): Yes that was the problem :) now its working! Maybe it should be pointed out in the example that this admin / credentials are an admin of that ldap. Thank you all :D
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#137
No description provided.