powered by Jive Software

Sleekxmpp component on openfire 3.8.2 - bad-namespace-prefix jabber:component:accept


I’m trying to register a component (made with python sleekxmpp) on openfire 3.8.2.

When connecting with sleekxmpp I can see the following in the logs:

DEBUG    SEND (IMMED): <stream:stream xmlns="jabber:component:accept" xmlns:stream="http://etherx.jabber.org/streams" to='foo'>
DEBUG    RECV: <stream:stream version="1.0" from="foobar.com" id="12345678">
DEBUG    SEND (IMMED): <handshake>blabla</handshake>
DEBUG    RECV: <stream:error xmlns="http://etherx.jabber.org/streams"><bad-namespace-prefix xmlns="urn:ietf:params:xml:ns:xmpp-streams" /></stream:error>
DEBUG    End of stream recieved

Then I saw the openfire log:

2013.08.27 12:53:40 org.jivesoftware.openfire.net.StanzaHandler - Closing session due to bad_namespace_prefix in stream header. Prefix: jabber:component:accept. Connection: org.jivesoftware.openfire.nio.NIOConnection@2a176ec6 MINA Session: (SOCKET [..])

Now I’m a bit confused because of: http://xmpp.org/extensions/xep-0114.html#proto

“xmlns=‘jabber:component:accept’” looks OK to me. Am I thinking wrong? Do I miss a piece of documentation for components?


Just saw http://community.igniterealtime.org/message/120201#120201 this in the “More like this” box. I will check this now first …


Problem was solved by defining a port for a component and use this in the client-component.