Then how to resolve this, please let me know if there is anything wrong in token generation. As I told you I do not have any domain so I am using IP in the URL as well as in the sub.
I have created the the token using https://www.jsonwebtoken.io/ this website.
Also please refer below the prosody settings for token.
Prosody version:0.11.6
Hi I have integrated with JWT and it was running also properly but today when i entered into room i got message “Authentication failed”.When i checked the error log i found in prosody log i.e:-“General warn Error verifing token error not-allowed reason:not acceptable by exp”.Please help me regrading this.
@emrah
jwt token integration failed with this error
Oct 01 18:04:06 modulemanager error Error initializing module ‘token_verification’ on ‘conference.meet.raleaa.com’: /usr/lib/prosody/util/startup.lua:199: module ‘basexx’ not found:Failed loading module basexx in LuaRocks rock basexx 0.4.1-1
no field package.preload[‘basexx’]
no file ‘/usr/lib/prosody/basexx.lua’
no file ‘/usr/local/share/lua/5.2/basexx.lua’
no file ‘/usr/local/share/lua/5.2/basexx/init.lua’
no file ‘/usr/local/lib/lua/5.2/basexx.lua’
no file ‘/usr/local/lib/lua/5.2/basexx/init.lua’
no file ‘/usr/share/lua/5.2/basexx.lua’
no file ‘/usr/share/lua/5.2/basexx/init.lua’
no file ‘/var/lib/prosody/.luarocks/share/lua/5.2/basexx.lua’
no file ‘/var/lib/prosody/.luarocks/share/lua/5.2/basexx/init.lua’
no file ‘/usr/lib/prosody/basexx.so’
no file ‘/usr/local/lib/lua/5.2/basexx.so’
no file ‘/usr/lib/x86_64-linux-gnu/lua/5.2/basexx.so’
no file ‘/usr/lib/lua/5.2/basexx.so’
no file ‘/usr/local/lib/lua/5.2/loadall.so’
no file ‘/var/lib/prosody/.luarocks/lib/lua/5.2/basexx.so’
stack traceback:
[C]: in function ‘_real_require’
/usr/lib/prosody/util/startup.lua:199: in function ‘require’
/usr/share/jitsi-meet/prosody-plugins/token/util.lib.lua:4: in main chunk
(…tail calls…)
…re/jitsi-meet/prosody-plugins/mod_token_verification.lua:24: in main chunk
[C]: in function ‘xpcall’
/usr/lib/prosody/core/modulemanager.lua:183: in function ‘do_load_module’
/usr/lib/prosody/core/modulemanager.lua:261: in function ‘load’
/usr/lib/prosody/core/modulemanager.lua:83: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/core/hostmanager.lua:108: in function ‘activate’
/usr/lib/prosody/core/hostmanager.lua:58: in function ‘?’
/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
(…tail calls…)
/usr/lib/prosody/util/startup.lua:391: in function ‘prepare_to_start’
/usr/lib/prosody/util/startup.lua:613: in function ‘f’
/usr/lib/prosody/util/async.lua:139: in function ‘func’
/usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
Jicofo 2020-10-01 21:06:46.636 SEVERE: [380] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP reconnection failed: No response received within reply timeout. Timeout was 15000ms (~15s). While waiting for establishing TLS
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:1248)
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.lang.Thread.run(Thread.java:748)
Jicofo 2020-10-01 21:06:46.638 SEVERE: [383] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.log() XMPP connection closed on error: input contained no data
Jicofo 2020-10-01 21:06:48.787 WARNING: [380] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.log() Failed to discover features for speakerstats.meet.raleaa.com: XMPP error reply received from speakerstats.meet.raleaa.com: XMPPError: service-unavailable - cancel
Jicofo 2020-10-01 21:06:48.788 WARNING: [380] org.jitsi.impl.protocol.xmpp.OpSetSimpleCapsImpl.log() Failed to discover features for conferenceduration.meet.raleaa.com: XMPP error reply received from conferenceduration.meet.raleaa.com: XMPPError: service-unavailable - cancel
When configure token in live it is not working, please help me.
Prosody log
Oct 03 14:00:57 c2s5627830006d0 info Client disconnected: closed
Oct 03 14:01:01 conference.online.connectz.ca:muc_domain_mapper warn Session filters applied
Oct 03 14:01:01 c2s5627834c1650 info Client connected
Oct 03 14:01:02 conference.online.connectz.ca:muc_domain_mapper warn Session filters applied
Oct 03 14:01:02 c2s562783077a20 info Client connected
Oct 03 14:01:04 c2s562783077a20 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Oct 03 14:01:04 c2s562783077a20 info Authenticated as jvb@auth.online.connectz.ca
Oct 03 14:01:04 c2s5627834c1650 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Oct 03 14:01:05 c2s5627834c1650 info Authenticated as focus@auth.online.connectz.ca
Oct 03 14:01:05 focus.online.connectz.ca:component warn Component not connected, bouncing error for:
Oct 03 14:01:11 conference.online.connectz.ca:muc_domain_mapper warn Session filters applied
Oct 03 14:01:11 mod_bosh info New BOSH session, assigned it sid ‘3b4374fe-c9f8-4dae-b4f8-95191637fd5a’
Oct 03 14:01:11 bosh3b4374fe-c9f8-4dae-b4f8-95191637fd5a warn No available SASL mechanisms, verify that the configured authentication module is working
Oct 03 14:01:35 bosh3b4374fe-c9f8-4dae-b4f8-95191637fd5a info BOSH client disconnected
Browser Log
Logger.js:154 2020-10-03T14:09:03.791Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Server did not yet offer a supported authentication mechanism. Sending a blank poll request.
I have tried to integrate same in Live server , but it not working. Please help.
Prosody Log
Oct 02 21:46:52 boshfb0a9092-3ab7-4aab-81e7-d58cdf54fa0a info BOSH client disconnected
Oct 03 06:52:36 conference.:muc_domain_mapper warn Session filters applied
Oct 03 06:52:36 mod_bosh info New BOSH session, assigned it sid ‘5fa6f72f-507f-450a-b9ce-dac910256146’
Oct 03 06:52:36 bosh5fa6f72f-507f-450a-b9ce-dac910256146 warn No available SASL mechanisms, verify that the configured authentication module is working
Oct 03 06:53:27 c2s560fa8e8af10 info Client disconnected: closed
Oct 03 06:53:32 conference.:muc_domain_mapper warn Session filters applied
Oct 03 06:53:32 c2s560fa8f1d170 info Client connected
Oct 03 06:53:33 c2s560fa8f1d170 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384)
Oct 03 06:53:33 c2s560fa8f1d170 info Authenticated as jvb@auth.
Browser console Log
2020-10-03T07:03:00.451Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Server did not yet offer a supported authentication mechanism. Sending a blank poll request.
o @ Logger.js:154
r.Strophe.log @ strophe.util.js:77
warn @ strophe.umd.js:1382
_no_auth_received @ strophe.umd.js:4823
_connect_cb @ strophe.umd.js:3245
_onRequestStateChange @ strophe.umd.js:5012
XMLHttpRequest.send (async)
d @ strophe.umd.js:5123
_processRequest @ strophe.umd.js:5137
_throttledRequestHandler @ strophe.umd.js:5290
_no_auth_received @ strophe.umd.js:4835
_connect_cb @ strophe.umd.js:3245
_onRequestStateChange @ strophe.umd.js:5012
XMLHttpRequest.send (async)
d @ strophe.umd.js:5123
_processRequest @ strophe.umd.js:5137
_throttledRequestHandler @ strophe.umd.js:5290
_no_auth_received @ strophe.umd.js:4835
_connect_cb @ strophe.umd.js:3245
_onRequestStateChange @ strophe.umd.js:5012
Logger.js:154 2020-10-03T07:04:00.732Z [modules/xmpp/strophe.util.js] <Object.r.Strophe.log>: Strophe: Server did not yet offer a supported authentication mechanism. Sending a blank poll request.