Problem with logging in with profile button

Hi, Jitsi developers, first of all, thank you so much for creating such a wonderful project.

I have been using Jitsi meet to host conferences. Everything worked fine for me. However, I have a problem with logging in.

I am using LDAP authentication method and docker-jitsi-meet stable-5765-1 version and my custom web front end.

I have no problem creating a room and starting meeting.

However, when a guest user tries to log in using the LDAP credentials into a created room, the application does not grant the moderator rights correctly. Below is the log when I try to do that.

2021-05-17T19:51:58.004Z [modules/xmpp/xmpp.js] <P._initStrophePlugins>:  P2P STUN servers:  
[{…}]
Logger.js:154 2021-05-17T19:51:58.007Z [modules/xmpp/xmpp.js] <P.connectionHandler>:  (TIME) Strophe connecting:	 16346.169999975245
content.bundle.js:523 Uncaught TypeError: Cannot read property 'source' of null
    at handleMessages (content.bundle.js:523)
react_devtools_backend.js:2557 2021-05-17T19:51:58.688Z [modules/xmpp/XmppConnection.js] <u._maybeEnableStreamResume>:  Stream resume enabled, but WebSockets are not enabled
Logger.js:154 2021-05-17T19:51:58.690Z [modules/xmpp/strophe.ping.js] <d.startInterval>:  XMPP pings will be sent every 10000 ms
Logger.js:154 2021-05-17T19:51:58.690Z [modules/xmpp/xmpp.js] <P.connectionHandler>:  (TIME) Strophe connected:	 17028.980000002775
Logger.js:154 2021-05-17T19:51:58.690Z [modules/xmpp/xmpp.js] <P.connectionHandler>:  My Jabber ID: [e-mail]/2-0kmCJX
react_devtools_backend.js:2557 2021-05-17T19:51:58.847Z [modules/xmpp/strophe.jingle.js] getting turn credentials with extdisco:2 failed, trying extdisco:1 
react_devtools_backend.js:2557 2021-05-17T19:51:59.006Z [modules/xmpp/strophe.jingle.js] getting turn credentials failed 
react_devtools_backend.js:2557 2021-05-17T19:51:59.007Z [modules/xmpp/strophe.jingle.js] is mod_turncredentials or similar installed and configured?

and here is the log from the web container on server

99.30.13.201 - - [17/May/2021:19:54:03 +0000] "POST /http-bind?room=undefined HTTP/2.0" 200 544 "https://example.meet.com/123" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
99.30.13.201 - - [17/May/2021:19:54:04 +0000] "POST /http-bind?room=undefined HTTP/2.0" 200 199 "example.meet.com" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"

I checked the redux store and the “features/base/connection”.connection.options.bosh is also “/http-bind?room=undefined” after attempting to login, but before I try to login the value of the field is ‘/http-bind?room=whateverNameIWant’, which is correct

[Zarawee]

yes, the Host can login perfectly.

[netzwerkgoettin]

Hi,

running 5870 Docker setup and nearly same problem – but I don’t use LDAP, I create prosody users.

• user goes to Settings -> Profile
• user clicks on Login
• user provides wrong credentials: user gets no error, login form remains open, error in Firefox console: 2021-06-09T21:33:28.947Z [connection.js] CONNECTION FAILED: connection.passwordRequired
• user clicks on cancel -> user is sent to close page and leaves the conference (which is a bug in my opinion, cancel should cancel the login process, not the whole conference)
• user provides correct credentials: prosody seems to recognize the user as valid, user is authenticated but does not gain moderator rights
• does not depend on Browser: Brave, Chrome, FF, Vivaldi, all the same effect
• it was working before, upgrading to 5870 crashed it

Regards, Marianne

Log from prosody Docker container:

c2s5576909942c0                                              info	Client connected
c2s5576909942c0                                              info	Authenticated as [e-mail]

Console Log Firefox:

@atlaskit/modal-dialog: Deprecation warning - Use of the footer prop in ModalDialog is deprecated. Please compose your ModalDialog using the 'components' prop instead Content.js:160:16
2021-06-09T21:35:41.170Z [modules/xmpp/xmpp.js] <_initStrophePlugins>:  P2P STUN servers:  
Array [ {…} ]
Logger.js:154:22
2021-06-09T21:35:41.173Z [modules/xmpp/xmpp.js] <connectionHandler>:  (TIME) Strophe connecting:	 13551 Logger.js:154:22
2021-06-09T21:35:41.494Z [modules/xmpp/XmppConnection.js] <_maybeEnableStreamResume>:  Enabling XEP-0198 stream management Logger.js:154:22
2021-06-09T21:35:41.494Z [modules/xmpp/XmppConnection.js] <_maybeStartWSKeepAlive>:  WebSocket keep alive interval: 60000ms Logger.js:154:22
2021-06-09T21:35:41.495Z [modules/xmpp/XmppConnection.js] <_maybeStartWSKeepAlive>:  Scheduling next WebSocket keep-alive in 86620.97450451064ms Logger.js:154:22
2021-06-09T21:35:41.495Z [modules/xmpp/strophe.ping.js] <startInterval>:  XMPP pings will be sent every 10000 ms Logger.js:154:22
2021-06-09T21:35:41.495Z [modules/xmpp/xmpp.js] <connectionHandler>:  (TIME) Strophe connected:	 13874 Logger.js:154:22
2021-06-09T21:35:41.495Z [modules/xmpp/xmpp.js] <connectionHandler>:  My Jabber ID: [e-mail]/_3zWT8Wh Logger.js:154:22
2021-06-09T21:35:41.558Z [modules/xmpp/strophe.jingle.js] <getStunAndTurnCredentials/<>:  getting turn credentials with extdisco:2 failed, trying extdisco:1 
<iq id="1a67bb72-c9c0-4fd4-9fd0-eb1d8d5a3426:sendIQ" type="error" from="meet.jitsi" xmlns="jabber:client" to="[e-mail]/_3zWT8Wh">
Logger.js:154:22
2021-06-09T21:35:41.593Z [modules/xmpp/strophe.jingle.js] <getStunAndTurnCredentials/</<>:  getting turn credentials failed 
<iq id="18f0165b-5ada-463b-aea5-f2cdd1ed4b5f:sendIQ" type="error" from="meet.jitsi" xmlns="jabber:client" to="[e-mail]/_3zWT8Wh">
Logger.js:154:22
2021-06-09T21:35:41.594Z [modules/xmpp/strophe.jingle.js] <getStunAndTurnCredentials/</<>:  is mod_turncredentials or similar installed and configured?