Hii @damencho, @Pawel_Domas,
I have added JWT authentication for jitsi meet. I added c2s_require_encryption = false in the prosody config file, also I have this configurations in /etc/prosody/conf.avail/myhost.domain.com.cfg.lua file and /etc/prosody/conf.d/myhost.domain.com.cfg.lua:
storage = "internal"
muc_room_cache_size = 100
Here are the logs for prosody:
| Apr 23 04:20:26 conference.meet.totalrecallsolutions.com:muc_domain_mapper | warn | Session filters applied |
|---|---|---|
| Apr 23 04:20:26 c2s561ba441cd40 | info | Client connected |
| Apr 23 04:20:28 c2s561ba441cd40 | info | Client disconnected: connection closed |
| Apr 23 05:25:41 conference.meet.totalrecallsolutions.com:muc_domain_mapper | warn | Session filters applied |
| Apr 23 05:25:41 mod_bosh | info | New BOSH session, assigned it sid ‘cef9d820-5bcd-4749-a901-8e3164aff652’ |
| Apr 23 05:25:41 boshcef9d820-5bcd-4749-a901-8e3164aff652 | warn | No available SASL mechanisms, verify that the configured authentication module ‘token’ is loaded and configured correctly |
| Apr 23 05:25:50 boshcef9d820-5bcd-4749-a901-8e3164aff652 | info | BOSH client disconnected: session close |
| Apr 23 05:40:50 conference.meet.totalrecallsolutions.com:muc_domain_mapper | warn | Session filters applied |
| Apr 23 05:40:50 mod_bosh | info | New BOSH session, assigned it sid ‘ad901621-8ef9-4d16-8357-92bd8c3e7664’ |
| Apr 23 05:40:50 boshad901621-8ef9-4d16-8357-92bd8c3e7664 | warn | No available SASL mechanisms, verify that the configured authentication module ‘token’ is loaded and configured correctly |
| Apr 23 05:41:08 boshad901621-8ef9-4d16-8357-92bd8c3e7664 | info | BOSH client disconnected: session close |
I am unable to start video and audio for the room.
Is my token authentication working? if no, then what I am doing wrong please suggest.