Closed Avatat closed 4 years ago
Problem solved. I will write a full solution soon!
LDAPauth was always hanging at DEBUG Checking group membership for bartosz.zieba
I sniffed LDAP communication and it looked like below:
No. Protocol Length Info
78 LDAP 155 bindRequest(1) "CN=Mumble,OU=Service,OU=Users,DC=xx,DC=yy,DC=zz" simple
79 LDAP 78 bindResponse(1) success
81 LDAP 203 searchRequest(2) "OU=Administrators,OU=Users,DC=xx,DC=yy,DC=zz" wholeSubtree
82 LDAP 250 searchResEntry(2) "CN=Bartosz Zięba,OU=Administrators,OU=Users,DC=xx,DC=yy,DC=zz" | searchResDone(2) success [1 result]
83 LDAP 227 searchRequest(3) "ou=Groups,dc=example,dc=org" wholeSubtree
84 LDAP 212 searchResDone(3) referral (0000202B: RefErr: DSID-03100835, data 0, 1 access points\n\tref 1: 'example.org'\n) [1 result]
I started wondering, what is ou=Groups,dc=example,dc=org
, and why LDAPauth is asking for it.
The answer was in LDAPauth.py:
default = { ...
('group_dn', str, 'ou=Groups,dc=example,dc=org'),
... }
So, I set group_dn
to CN=Mumble Users,OU=Apps,OU=Groups,DC=xx,DC=yy,DC=zz
, and LDAPauth started going further with LDAP communication:
No. Protocol Length Info
44 LDAP 155 bindRequest(1) "CN=Mumble,OU=Service,OU=Users,DC=xx,DC=yy,DC=zz" simple
45 LDAP 78 bindResponse(1) success
47 LDAP 199 searchRequest(2) "OU=Administrators,OU=Users,DC=xx,DC=yy,DC=zz" wholeSubtree
48 LDAP 248 searchResEntry(2) "CN=Bartosz Zięba,OU=Administrators,OU=Users,DC=xx,DC=yy,DC=zz" | searchResDone(2) success [2 results]
49 LDAP 260 searchRequest(3) "CN=Mumble Users,OU=Apps,OU=Groups,DC=xx,DC=yy,DC=zz" wholeSubtree
50 LDAP 196 searchResEntry(3) "CN=Mumble Users,OU=Apps,OU=Groups,DC=xx,DC=yy,DC=zz" | searchResDone(3) success [2 results]
51 LDAP 158 bindRequest(4) "CN=Bartosz Zięba,OU=Administrators,DC=xx,DC=yy,DC=zz" simple
52 LDAP 78 bindResponse(4) success
Success! All of our users could securely connect to the new Mumble server using their LDAP credentials. Mumble stays private and secured.
Hello Mumble Crew! I would love to start using Mumble as VoIP platform for remote working employees in the company where I work, but I have a problem, which is blocking me:
I have a fresh installation of Murmur
1.3.0-1~ppa1~bionic1
. When I join the server without any authorization, everything works flawlessly, I can see created channels and I can speak with other users. Murmur log looks as below:The problem begins, when I enable LDAPauth.py with this config:
After successfull connection to the server, I see only
Root
channel, and I see no users (even me). After ~15 seconds, the connection interrupt and the client try to reconnect. Murmur server log:LDAPauth log:
Mumble client log:
As you can see, the server log ends differently than in the previous case (without LDAPauth), there is no
Starting voice thread
and later lines.How can I dig it deeper? If the patch is needed, I would like to contribute and help the project, but I don't know where to start.