Authentication failed using jwt

Hi,

I followed this article to setup token authentication: https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md
I’m using this jitsi meet api to load in iframe or open direct on navigator tab: https://github.com/jitsi/jitsi-meet/blob/master/doc/api.md

I generate a jwt token and validate it using jwt.io to decode and has no problem with token, but when using on my jitsi meet, is showed a notification with Authentication failed message.

This is my data in jwt token:

const header = {
‘alg’: ‘HS256’,
‘typ’: ‘JWT’
};

const data = {
‘context’: {
‘group’: ‘xxxxxx’,
‘user’: {
‘id’: 1337,
‘username’: ‘user123’,
‘name’: ‘Silas Ribas’,
‘avatar’: ‘https://www.gravatar.com/avatar/b0c193ec258695f17dabdbf2e09bdbcd.jpg?s=200’,
},
‘callee’: {
‘id’: 2222,
‘username’: ‘user777’,
‘name’: ‘Teofilo da Silva’,
‘avatar’: ‘https://sjc3.discourse-cdn.com/business4/user_avatar/community.jitsi.org/kent_safranski/180/10385_2.png’,
}
},
‘iss’: ‘myapp’,
‘room’: ‘Rom123’,
‘sub’: ‘meet.myapp.com.br’,
‘aud’: ‘myapp’
};

  • My room is replaced to “Rom123” fro security.
    ** “myapp” original string is my issuer, audience, app_id and my domain.
    *** Group is random.

Any idea? Or how to debug this jwt verifcation?

Don’t fill group. Remove the field.
With the group the link should be https://meet.myapp.com.br/xxxxxx/Rom123

Hi,

I remove but continue to fail.

My token on jwt.io decode:

My jitsi meet screen with authentication failed message:

Anything in the logs? I had similar issues with bad prosody configuration and had to check the logs

When I access my meet with jwt no messages appear in prosody log, but when I restart prosody, this messages appear in /var/log/prosody/prosody.err:

Apr 03 12:03:03 portmanager error Failed to open server port 5269 on ::, check that Prosody or another XMPP server is not already running and using this port
Apr 03 12:03:03 portmanager error Failed to open server port 5269 on *, check that Prosody or another XMPP server is not already running and using this port
Apr 03 12:03:03 portmanager error Failed to open server port 5347 on 127.0.0.1, this port is in use by another application
Apr 03 12:03:03 portmanager error Failed to open server port 5347 on ::1, this port is in use by another application
Apr 03 12:03:03 portmanager error Failed to open server port 5222 on ::, check that Prosody or another XMPP server is not already running and using this port
Apr 03 12:03:03 portmanager error Failed to open server port 5222 on *, check that Prosody or another XMPP server is not already running and using this port
Apr 03 12:03:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Check that the permissions allow Prosody to read this file. (for localhost)
Apr 03 12:03:03 localhost:tls error Error creating context for c2s: error loading private key (Permission denied)
Apr 03 12:03:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
Apr 03 12:03:03 localhost:tls error Error creating contexts for s2sout: error loading private key (system lib)
Apr 03 12:03:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
Apr 03 12:03:03 localhost:tls error Error creating contexts for s2sin: error loading private key (system lib)
Apr 03 12:03:03 portmanager error Failed to open server port 5280 on ::, check that Prosody or a BOSH connection manager is not already running
Apr 03 12:03:03 portmanager error Failed to open server port 5280 on *, check that Prosody or a BOSH connection manager is not already running
Apr 03 12:03:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Check that the permissions allow Prosody to read this file. (for localhost)
Apr 03 12:03:03 portmanager error Error creating TLS context for SNI host localhost: error loading private key (Permission denied)
Apr 03 12:03:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/localhost.key’: Previous error (see logs), or other system error. (for localhost)
Apr 03 12:03:03 portmanager error Error creating TLS context for SNI host localhost: error loading private key (system lib)

I check and /etc/prosody/certs/localhost.key don’t exists.

Any other log I need to see?

Well, if Prosody needs the localhost.key and it’s not there or not accessible… you don’t still need to see any other log, you need to solve that issue first and see what happens.
Anyway if prosody cannot open ports it looks like a different issue but I would try fixing the localhost.key problem first.

Some error messages with jwt are seen only if you inspect the returned error packets, open chrome developer console, network tab and try to join with jwt and find the bosh error message and read the response xmpp.

But my installation and configuration is automatically using ubuntu repository package (I follow this article https://aws.amazon.com/pt/blogs/opensource/getting-started-with-jitsi-an-open-source-web-conferencing-solution/). Most of all configuration is generated by installation process.

In manual install tutorial don’t show configuration about localhost: https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md

I solve localhost certs error with this steps:
chmod 0640 /etc/prosody/certs/localhost.*
chown root:prosody /etc/prosody/certs/localhost.*
ln -s /var/lib/prosody/localhost.crt /usr/local/share/ca-certificates/localhost.crt
update-ca-certificates -f

I open on iptables on ubuntu and on network service rules all 3 ports and continue errors.

Any idea?

I’ll trying to debug this.

I check and see 2 prosody’s instances. Kill all and start one and its ok about ports problem.

Now has this:

internal.auth.meet.domain.com.br:muc error Error restoring room jvbbrewery@internal.auth.meet.domain.com.br from storage: no data storage active

Hi,

In change storage to “memory” in “internal.auth.xxx.xxx.xx” config.
Execute this, after see https://community.jitsi.org/t/jwt-authantication-failed/21681/12:
sed -i ‘s/module:hook/module:hook_global/g’ /usr/share/jitsi-meet/prosody-plugins/mod_auth_token.lua

Authentication is succefully now.
My prosody (prosodyctl about): Prosody trunk nightly build 1247 (2020-04-01, 0230ceecb8a9)

But this error occur and jitsi meet down and try reconnect again and again:

Apr 04 03:10:31 c2s5589076821a0 error Traceback[c2s]: /usr/lib/prosody/util/cache.lua:66: table index is nil
stack traceback:
/usr/lib/prosody/util/cache.lua:66: in function ‘set’
/usr/lib/prosody/modules/muc/mod_muc.lua:185: in function ‘track_room’
/usr/lib/prosody/modules/muc/mod_muc.lua:213: in function </usr/lib/prosody/modules/muc/mod_muc.lua:200>
(tail call): ?
/usr/lib/prosody/modules/muc/mod_muc.lua:446: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(tail call): ?
/usr/lib/prosody/core/stanza_router.lua:188: in function ‘core_post_stanza’
/usr/lib/prosody/core/stanza_router.lua:128: in function ‘core_process_stanza’
/usr/lib/prosody/modules/mod_c2s.lua:283: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>

Hi,

Change storage to “memory” in Component “conference.meet.benjimed.com.br” stop to restart again and again.

Everything apparently fine, but in prosody error log has:

mod_bosh error Traceback[bosh]: /usr/lib/prosody/util/stanza.lua:62: invalid text value: expected string, got number

I’m searching about this.
Thks

We’d got some of the problems you explain in our last deploy (had conference…com’s storage as “memory” but internal.auth…com’s storage as “none”) and had to change prosody configs (set internal.auth…com’s storage to “memory”).
That last stanza.lua error does not seem very important. Did not go very deep into it but having a quick look at the file (https://github.com/bjc/prosody/blob/master/util/stanza.lua) it looks like you could be using a number in some field expected to be string (name of participants? name of the room?).

1 Like

Hi,

About using number, in my payload I using number on user.id and callee.id:
‘context’: {
‘user’: {
‘id’: 1337,

},
‘callee’: {
‘id’: 2222,

}
},

I change to string and problem is solved!
Thanks!!

1 Like

Hii everyone…

i am using authentication with prosody connect with MySQL and its connected also but
not initiating room still same wait for moderator

my console log is

2020-05-20T06:28:52.691Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:28:52.696Z [modules/xmpp/xmpp.js] <A.connectionHandler>: (TIME) Strophe disconnecting: 24868.740000005346
Logger.js:154 2020-05-20T06:28:52.698Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Disconnect was called because: undefined
s @ md5.js:1
Logger.js:154 2020-05-20T06:28:52.700Z [modules/xmpp/moderator.js] <u.setFocusUserJid>: Focus jid set to: undefined
Logger.js:154 2020-05-20T06:28:52.701Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:28:53.932Z [modules/xmpp/xmpp.js] <A.connectionHandler>: (TIME) Strophe disconnected: 26105.18499999307
Logger.js:154 2020-05-20T06:28:54.124Z [modules/xmpp/moderator.js] <u.setFocusUserJid>: Focus jid set to: focus@auth.example.com
Logger.js:154 2020-05-20T06:28:54.124Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:28:54.125Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:28:54.125Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:28:54.128Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:28:54.128Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 1000
Logger.js:154 2020-05-20T06:28:54.739Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:28:55.131Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:28:55.262Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:28:55.262Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:28:55.263Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:28:55.264Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:28:55.264Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 2000
Logger.js:154 2020-05-20T06:28:55.624Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:28:55.624Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:28:55.625Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:28:55.625Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:28:55.625Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 4000
Logger.js:154 2020-05-20T06:28:57.265Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:28:57.600Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:28:57.600Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:28:57.601Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:28:57.601Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:28:57.602Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 8000
Logger.js:154 2020-05-20T06:28:59.627Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:29:00.079Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:29:00.080Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:29:00.080Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:29:00.080Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:29:00.081Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 16000
Logger.js:154 2020-05-20T06:29:05.609Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:29:05.927Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:29:05.929Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:29:05.930Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:29:05.931Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:29:05.932Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 32000
Logger.js:154 2020-05-20T06:29:16.082Z [modules/xmpp/moderator.js] <u.createConferenceIq>: Session ID: 81f4bafe-7e26-4267-b30c-3d15212bf001 machine UID: b4193cc85713049191fa56e56b4c8f5b
Logger.js:154 2020-05-20T06:29:16.491Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Authentication enabled: true
Logger.js:154 2020-05-20T06:29:16.492Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: External authentication enabled: false
Logger.js:154 2020-05-20T06:29:16.492Z [modules/xmpp/moderator.js] <u.parseSessionId>: Received sessionId: 81f4bafe-7e26-4267-b30c-3d15212bf001
Logger.js:154 2020-05-20T06:29:16.494Z [modules/xmpp/moderator.js] <u.parseConfigOptions>: Sip gateway enabled: false
Logger.js:154 2020-05-20T06:29:16.494Z [modules/xmpp/moderator.js] <u._allocateConferenceFocusSuccess>: Waiting for the focus… 64000

and my jvb log is

020-05-20 02:31:14.550 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.00384S. Sticky failure: false
2020-05-20 02:31:24.546 INFO: [20] Videobridge.createConference#320: create_conf, id=c0be9972207fa0b0 gid=null logging=false
2020-05-20 02:31:24.549 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.003566S. Sticky failure: false
2020-05-20 02:31:34.546 INFO: [20] Videobridge.createConference#320: create_conf, id=ce2432a10681a75e gid=null logging=false
2020-05-20 02:31:34.550 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.00431S. Sticky failure: false
2020-05-20 02:31:44.546 INFO: [20] Videobridge.createConference#320: create_conf, id=1493c7ab8dd98252 gid=null logging=false
2020-05-20 02:31:44.551 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.004624S. Sticky failure: false
2020-05-20 02:31:54.373 INFO: [18] VideobridgeExpireThread.expire#144: Running expire()
2020-05-20 02:31:54.546 INFO: [20] Videobridge.createConference#320: create_conf, id=b43b3acd419493e8 gid=null logging=false
2020-05-20 02:31:54.550 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.003859S. Sticky failure: false
2020-05-20 02:32:04.547 INFO: [20] Videobridge.createConference#320: create_conf, id=6ddb706d51b8b8c gid=null logging=false
2020-05-20 02:32:04.551 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.004265S. Sticky failure: false
2020-05-20 02:32:14.546 INFO: [20] Videobridge.createConference#320: create_conf, id=1aa41022a0dedf6a gid=null logging=false
2020-05-20 02:32:14.549 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.003599S. Sticky failure: false
2020-05-20 02:32:24.546 INFO: [20] Videobridge.createConference#320: create_conf, id=8a449ef481e4ad6b gid=null logging=false
2020-05-20 02:32:24.550 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.003703S. Sticky failure: false
2020-05-20 02:32:34.547 INFO: [20] Videobridge.createConference#320: create_conf, id=1a161de36e9f375f gid=null logging=false
2020-05-20 02:32:34.552 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.005786S. Sticky failure: false
2020-05-20 02:32:44.546 INFO: [20] Videobridge.createConference#320: create_conf, id=68d549a776326e77 gid=null logging=false
2020-05-20 02:32:44.550 INFO: [20] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.003758S. Sticky failure: false

my jicofo.log

Jicofo 2020-05-20 04:03:43.853 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 6
Jicofo 2020-05-20 04:03:44.853 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 5
Jicofo 2020-05-20 04:03:45.854 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 4
Jicofo 2020-05-20 04:03:46.854 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 3
Jicofo 2020-05-20 04:03:47.854 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 2
Jicofo 2020-05-20 04:03:48.855 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 1
Jicofo 2020-05-20 04:03:49.855 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 0
Jicofo 2020-05-20 04:03:49.855 INFO: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectingIn().586 XMPP reconnecting in: 0
Jicofo 2020-05-20 04:03:49.955 WARNING: [612] org.jitsi.impl.protocol.xmpp.PacketDebugger.log().121 Smack: Reconnection failed due to an exception (XMPPTCPConnection[focus@auth.example.c$
org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: not-authorized
at org.jivesoftware.smack.SASLAuthentication.authenticationFailed(SASLAuthentication.java:292)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1100)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(XMPPTCPConnection.java:1000)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:1016)
at java.base/java.lang.Thread.run(Thread.java:834)
Jicofo 2020-05-20 04:03:49.956 SEVERE: [612] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.reconnectionFailed().592 XMPP reconnection failed: SASLError using SCRAM-SHA-1: not-authorized

my prosody.log

May 20 03:53:35 c2s5629af382800 info Client connected
May 20 03:53:35 c2s5629af382800 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
May 20 03:53:41 conference.example.com:muc_domain_mapper warn Session filters applied
May 20 03:53:41 c2s5629aed1f410 info Client connected
May 20 03:53:41 c2s5629aed1f410 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
May 20 03:58:35 c2s5629af382800 info Client disconnected: connection closed
May 20 03:58:41 c2s5629aed1f410 info Client disconnected: connection closed
May 20 03:58:42 conference.example.com:muc_domain_mapper warn Session filters applied
May 20 03:58:42 c2s5629aed49760 info Client connected
May 20 03:58:42 c2s5629aed49760 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
May 20 03:58:51 conference.example.com:muc_domain_mapper warn Session filters applied
May 20 03:58:51 c2s5629ae995180 info Client connected
May 20 03:58:51 c2s5629ae995180 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
May 20 04:03:42 c2s5629aed49760 info Client disconnected: connection closed
May 20 04:03:49 conference.example
.com:muc_domain_mapper warn Session filters applied
May 20 04:03:49 c2s5629af5fb4a0 info Client connected
May 20 04:03:49 c2s5629af5fb4a0 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
May 20 04:03:51 c2s5629ae995180 info Client disconnected: connection closed
May 20 04:04:01 conference.example.com:muc_domain_mapper warn Session filters applied
May 20 04:04:01 c2s5629af0f9dd0 info Client connected
May 20 04:04:01 c2s5629af0f9dd0 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)