XMPP with ISPConfig

Discussion in 'Developers' Forum' started by theWeird, Feb 20, 2015.

  1. Gerd

    Gerd New Member

    Hi,
    thank you for adding the XMPP function to ISPConfig. I would love to use it, but i do not manage to get it working. Perhaps you can give me a hint where to look for the error.

    It seems as the client (ihave tried gajim, pidgin, conversations and empaty) try to get a list of auth mechanisms and metronome is not willing to send it?

    In /etc/metronome/metronome.dbg get:

    c2sebfcd0 debug Received[c2s_unauthed]: <iq id='7' type='get'>
    mod_router debug Stanza of type iq from c2s_unauthed has xmlns: jabber:iq:auth
    mod_router debug Unhandled c2s_unauthed stanza: iq; xmlns=jabber:iq:auth

    When i log the jabber conversation from the client side i get:

    SENDING: <iq type='get' id='purpledb857591'><query xmlns='jabber:iq:auth'><username>XY</username></query></iq>
    RECEIVED: (137): <iq id='purpledb857591' type='error'><error type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

    The metronome external auth command /usr/lib/metronome/isp-modules/mod_auth_external/authenticate_isp.sh is never called by metronome.

    Best regards,

    Gerd
     
  2. ccoudsi

    ccoudsi New Member

    Hi Guys,
    I just updated my ISPConfig to Version: 3.1.2 on my ubuntu 16.04, and now lost my Metronome/Turn server, I removed and added new domain and users, I get an error message from my client says "Server not compatible" then I went back and updated all the files per this thread now i'm getting user not authorized I'm 100% sure the xmpp user password of the client match the server xmpp user password !!!
    Code:
    Feb 05 11:42:59 socket  debug   accepted incoming client connection from: xxx.xxx.183.53 54267 to 5222
    Feb 05 11:42:59 c2s1917f40      info    Client connected
    Feb 05 11:42:59 c2s1917f40      debug   Client sent opening <stream:stream> to xxxx.com
    Feb 05 11:42:59 c2s1917f40      debug   Sent reply <stream:stream> to client
    Feb 05 11:42:59 c2s1917f40      debug   Received[c2s_unauthed]: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'>
    Feb 05 11:42:59 socket  debug   try to start ssl at client id: 1917f40
    Feb 05 11:42:59 socket  debug   ssl session delayed until writebuffer is empty...
    Feb 05 11:42:59 c2s1917f40      debug   TLS negotiation started for c2s_unauthed...
    Feb 05 11:42:59 socket  debug   starting ssl handshake after writing
    Feb 05 11:42:59 socket  debug   starting handshake...
    Feb 05 11:42:59 socket  debug   ssl handshake of client with id:table: 0x1917f40, attempt:1
    Feb 05 11:42:59 socket  debug   ssl handshake of client with id:table: 0x1917f40, attempt:2
    Feb 05 11:42:59 socket  debug   ssl handshake of client with id:table: 0x1917f40, attempt:3
    Feb 05 11:42:59 socket  debug   ssl handshake done
    Feb 05 11:42:59 c2s1917f40      debug   Client sent opening <stream:stream> to xxxxx.com
    Feb 05 11:42:59 c2s1917f40      debug   Sent reply <stream:stream> to client
    Feb 05 11:42:59 c2s1917f40      debug   Received[c2s_unauthed]: <auth mechanism='PLAIN' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
    Feb 05 11:42:59 xxxxx.com:auth_external        debug   test_password check: admin xxxxxxxxxxx
    Feb 05 11:42:59 xxxxx.com:auth_external        debug   Opening process /usr/lib/metronome/isp-modules/mod_auth_external/authenticate_isp.sh
    Feb 05 11:42:59 xxxxx.com:auth_external        debug   send_query check: auth:admin:xxxxx.com:xxxxxxxxxx
    
    Feb 05 11:42:59 xxxx.com:saslauth     debug   sasl reply: <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text>Unable to authorize you with the authentication credentials you&apos;ve sent</text></failure>
    
     
    Last edited: Feb 5, 2017

Share This Page