question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when LDAP authentication is enabled

See original GitHub issue

Hello, I tried to enable LDAP authentication with this docker compose setup, but something went wrong. I followed instructions in this ticket https://github.com/jitsi/jitsi-meet/issues/2757. It seems Prosody works well, but I can’t figure out why I get an error as shown in the picture:

jitsi_20190123_093146

Here is my configuration:

  1. I built https://github.com/luaforge/lualdap directly inside Prosody container, with build-essential libldap2-dev liblua5.1.0-dev packages installed.
  2. Then I rebuilt the container and mount volumes with modules and the library:
prosody:
  ...
  volumes:
    ...
    - ${CONFIG}/prosody-modules:/modules
    - ${CONFIG}/prosody-libs:/usr/lib/lua/5.1
  1. Here is the modified jitsy-meet/prosody/prosody.cfg
...
consider_bosh_secure = true
...
plugin_paths = { "/modules" }
  1. There is nothing special in jitsy-meet/prosody/conf.d/ldap.cfg
  2. Here is the modified jitsy-meet/prosody/conf.d/jitsy-meet.cfg
VirtualHost "meet.jitsi"
    authentication = "ldap2"
    ...

VirtualHost "guest.meet.jitsi"
    authentication = "anonymous"
  1. I also uncommented the line in web/config.js
hosts: {
  ...
  anonymousdomain: 'guest.meet.jitsi',
  ...
}
  1. Here is the complete log output from docker-compose when I’m trying to become a host: jitsi.log.txt

Can anyone please advise what I missed here?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
alexcustoscommented, Jan 24, 2019

Thank you again, LDAP authentication is working perfectly now. I posted a PR and commented on the recommended PR #50 to highlight issues I faced while tried to apply it to my setup. Hope it will save some time for someone.

0reactions
alexcustoscommented, Jun 17, 2019

Hello @hardiyan46, Unfortunately, I failed to bind this container with OpenPaaS that time due to another issue, and don’t use Jitsy anymore. But if I remember correctly, they released this feature officially, so it worth to check the documentation.

Read more comments on GitHub >

github_iconTop Results From Across the Web

LDAP authentication setup without error but users can not ...
The authentication will fail as there is not an LDAP server running on the appliance.
Read more >
LDAP client authentication failed - SonicWall
One of the most common errors encountered when configuring LDAP is authentication failed. This article will detail what that error means as well...
Read more >
LDAP Authentication error: Login was not successful
For LDAP authentication, user accounts are not visible or configurable on an individual basis in Serv-U. Instead, LDAP Group membership is used ...
Read more >
Receiving "ldap operation failed: failed to bind as user" error ...
Introduction Problem When the LDAP authentication method is configured, the first Vault client login via the newly configured LDAP...
Read more >
Troubleshooting user login issues with LDAP authentication
This error indicates that LDAP authentication is enabled but the user cannot be authenticated. Do the following: Check the Application Server ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found