[jdev] jabber:iq:auth in the component:accept namespace?
Matthias Wimmer
m at tthias.net
Thu Aug 18 06:57:39 CDT 2005
Hi Konstantin!
The problem with your approach is that as a component you always have to
send fully addressed stanzas including a source address. Your stanza is
missing the from attribute. The session manager would not be able to
send anything back to you.
From the log message I am assuming you are using jabberd 1.4.x. You can
get a client session from a component using the protocol the client
connection manager is talking to the session manager. This is quickly
documented in http://svn.jabberd.org/trunk/jadc2s/PROTO
Starting with jabberd 1.4.5 you will in addition to this protocol also
be able to use the protocol of the jabberd2 session manager which is
documented in http://jabberd.jabberstudio.org/dev/docs/session.shtml
Please note that both protocols are implementation internals, so your
component won't be portable to other implementations, that might have
other internal protocols.
Tot kijk
Matthias
Konstantin Klyagin wrote:
>I investigated a little bit more on the possibility for a component
>to pretent to be a user. From a connected service, I tried to send
>a regular jabber:iq:auth iq set packet. Whatever the packet looked
>like, it was ignored by the Jabber server with the following log
>message:
>
>20050818T10:13:10: [warn] (-internal): Packet Delivery Failed,
>invalid packet, dropping <iq type='set'
>to='xxxx.net'><query
>xmlns='jabber:iq:auth'><username>xxx</username><password>xxx</password></query></iq>
>
>I am wondering if it's completely impossible to operate a component
>and a client within the same XML stream, so I have to open a new
>connection for every client, or if there is still a way to do so?
>
>Thanks.
>
>
>
More information about the JDev
mailing list