![]() Despite trying with just one jvb, the system is still failing. I attempted to configure jvb, prosody, and jicofo, but none of these configurations have been successful. TURNCREDENTIALS_SECRET: amljaWZvY29tcG9uZW50 JICOFO_AUTH_PASSWORD: amljaWZvY29tcG9uZW50 JICOFO_COMPONENT_SECRET: amljaWZvY29tcG9uZW50 Any advice or suggestions would be greatly appreciated. I am new to both Jitsi and Kubernetes, so please excuse any perceived lack of expertise. I have noticed that multiple participants can join and engage in chat via Firefox and Chrome, but they are unable to see or hear each other. I am running this setup on my local machine, using minikube on Ubuntu, which is deployed on a VMware workstation. I have attached my YAML files and would appreciate it if someone could review them and let me know if there are any configuration elements that may be missing. I am not a member of any organization, so I am turning to the Jitsi community for assistance. Our ideal state is that LDAP users can start a conference and then anyone can join.Īgain, thank you all for helping with this documentation.I am currently working on a personal project to better understand Kubernetes and Jitsi, and I could use some help with my setup. Having LDAP work for hosts and guests at least makes my server (more) secure. Is that part of the equation? Do I need to have a subdomain (not so easy, actually) or do I need to just create another host?Įg: do I need to add something to /etc/hosts ? My main virtual host is …īut I didn’t create guest as a hostname externally or internally on my DNS servers. I’m starting to think this is a hostname thing. If I add the virtual host for anonymous guests, then it opens up my entire server for everyone. If I follow the Github guide, I can get LDAP auth working for hosts. This feels very valuable and I want to start with appreciation for y’all! I’ll speak personally- I’m standing up servers for healthcare uses. I suspect many of us are new Jitsi users because of the COVID-19 pandemic. I added the prosody to sasl group with the command:įirst I just want to thank Balu and others on this thread. I wonder if other people have similar experiences. In the end I gave up on the LDAP2 method and went for the other option with Cyrus.įollowed the steps you described and it worked like a charm the first way round. I tried to limit the search by creating all kinds of filters me and Google could come up with, without any result. The error logs stated a fatal error in one of the LUA LDAP libraries when it tries to retrieve a non existent attribute. Limiting the search to one OU worked fine. Due to design of our AD it has to look in multiple OU’s, which it seems not to be handled well by ldap2. ![]() Prosody chocked on finding the user, that didn’t exists. I spend a few hours one trying to get the first method to work.Īt first it seemed to work, until a wrong user / password combination was entered. Today I spent most of my day setting up a new Jitsi environment with LDAP support. Thank you for putting your findings in one single wiki page! Logger.js:154 T13:55:04.534Z : External authentication enabled: false Logger.js:154 T13:55:04.533Z : Authentication enabled: false It seems strange that the console log is logging: /etc/jitsi/jicofo/sip-communicator.properties (adding the XMPP: line)./etc/prosody/conf.avail/ (adding the VirtualHost anonymous). ![]()
0 Comments
Leave a Reply. |