SASLError using SCRAM-SHA-1: not-authorized

Developers
1

Hello,
/var/log/jitsi/jvb.log is quite large. It gets updated every 5 seconds with these lines:

JVB 2023-01-27 11:36:29.694 INFORMAZIONI: [29] [hostname=localhost id=shard] MucClient$2.connectionClosed#334: Closed.
JVB 2023-01-27 11:36:31.355 AVVERTENZA: [35] [hostname=localhost id=shard] MucClient.setPresenceExtensions#467: Cannot set presence extension: not connected.
JVB 2023-01-27 11:36:34.769 INFORMAZIONI: [29] [hostname=localhost id=shard] MucClient$2.connected#321: Connected.
JVB 2023-01-27 11:36:34.769 INFORMAZIONI: [29] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$9#646: Logging in.
JVB 2023-01-27 11:36:34.808 AVVERTENZA: [29] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$9#660: Failed to login. Disconnecting to trigger a re-connect.
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
	at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:286)
	at org.jivesoftware.smack.AbstractXMPPConnection.lambda$new$2(AbstractXMPPConnection.java:407)
	at org.jivesoftware.smack.NonzaCallback$ClassAndConsumer.accept(NonzaCallback.java:177)
	at org.jivesoftware.smack.NonzaCallback$ClassAndConsumer.access$200(NonzaCallback.java:166)
	at org.jivesoftware.smack.NonzaCallback.onNonzaReceived(NonzaCallback.java:46)
	at org.jivesoftware.smack.AbstractXMPPConnection.parseAndProcessNonza(AbstractXMPPConnection.java:1440)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection.access$1700(XMPPTCPConnection.java:131)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1010)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:916)
	at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:939)
	at java.base/java.lang.Thread.run(Thread.java:829)

What does this means?

Thank you,
Giuseppe

2

JVB can’t login to Prosody. Most probably the XMPP login credentials for the videobridge user don’t match with the ones set up in Prosody.

1 Like
3

I think I did not setup any account, then only the default ones should be currently used. I checked that on this system prosody stores all accounts on the file system, in /var/lib/prosody/auth%2eMYHOSTNAME/accounts/ . Over there only two files are present: focus.dat and jvb.dat.
focus username and password seems to be stored in /etc/jitsi/jicofo/jicofo.conf.
I could not find where the jvb password is stored among the jvb configuration files.

Should I find where these user and password are configured in jvb and update them with a new password that I should also change with prosodyctl for jvb user?

Thank you,
Giuseppe

4

Check in /etc/jitsi/videobridge/sip-communicator.properties
Look for “username” and “password”.
Also check the hostname and the xmpp domain - in fact all the settings under “org.jitsi.videobridge.xmpp.user.*” are related to the xmpp connection.

5

Thank you. At the same time I’ve found that file used in the Debian postinst script. I updated the password with prosody and restarted it. Now the jvb log does not contain complains any more.

Thank you again.
Giuseppe

1 Like
6

may i ask how to update the password with prosody and restart it? i have the same problem. sorry im new to this

7

I used the command

prosodyctl passwd jvb@auth.DOMAIN

Of course, replace DOMAIN with your domain name as shown in /etc/jitsi/videobridge/sip-communicator.properties

2 Likes