ProcessOne SiteCustomer Helpdesk and FeedbackFollow us on Twitter
 
   
 
Tsung Authentication ERROR
Posted: 01 November 2011 06:10 PM   [ Ignore ]
Junior Member
Avatar
RankRank
Total Posts:  38
Joined  2009-11-19

Using Tsung and latest ejabberd 2.1.x, I can connect the users but not authenticate them.

<session probability="100" name="jabber-example" type="ts_jabber">

    <
request> <jabber type="connect" ack="no_ack"></jabber> </request>
    <
thinktime value="3"></thinktime>
    <
transaction name="authenticate">
      <
request> <jabber type="auth_get" ack="local"></jabber> </request>
      <
request> <jabber type="auth_set_plain" ack="local"></jabber> </request>
    </
transaction>

    <
thinktime value="10"></thinktime>

    <
request>
        <
jabber type="raw" ack="no_ack" data="<iq id='zid615d9' to='+6736733@test.test.com' type='get'><contacts ></iq>"></jabber>
    </
request>

    <
thinktime value="10"></thinktime>

    <
transaction name="online">
    <
request> <jabber type="chat" ack="no_ack" size="16" destination="online"></jabber> </request>
    </
transaction>

    <
thinktime value="10"></thinktime>

    <
transaction name="close">
      <
request> <jabber type="close" ack="no_ack"></jabber> </request>
    </
transaction>
  </
session

I can see an error on ejabberd log:

=INFO REPORT==== 2011-11-01 17:50:44 ===
D(<0.1635.0>:ejabberd_receiver:320) : Received XML on stream = “<iq id=‘88’ type=‘get’ ><query ><username>tsung22</username></query></iq>”

=INFO REPORT==== 2011-11-01 17:50:44 ===
D(<0.1635.0>:shaper:61) : State: {maxrate,1000,0,1320166242682072}, Size=95
M=47.5, I=2002.601


=INFO REPORT==== 2011-11-01 17:50:44 ===
D(<0.1636.0>:ejabberd_c2s:1553) : Send XML on stream = <<”<iq from=‘test.test’ id=‘88’ type=‘error’><error code=‘503’ type=‘cancel’><service-unavailable ></error></iq>”>>

Profile
 
 
Posted: 03 November 2011 03:45 PM   [ Ignore ]   [ # 1 ]
Moderator
RankRank
Total Posts:  38
Joined  2009-06-04

Hi,

most likely the tsung version you use suffer from this bug:

http://lists.process-one.net/pipermail/tsung-users/2010-November/001577.html

I checked and it is still there on current tsung version.  I’ll be sending a patch,  but meantime if you want to use legacy auth, I suggest the easiest way is to edit   tsung_jabber_common.erl,  and remove the line that sends version=“1.0”  on the connect() function

Profile
 
 
Posted: 09 November 2011 01:01 PM   [ Ignore ]   [ # 2 ]
Junior Member
Avatar
RankRank
Total Posts:  38
Joined  2009-11-19

Question, remove the entire line that sends, or just the 1.0 version attribute?

Thanks,

Profile
 
 
Posted: 09 November 2011 02:46 PM   [ Ignore ]   [ # 3 ]
Moderator
RankRank
Total Posts:  38
Joined  2009-06-04

yes, sorry,  only the “version=‘1.0’”  part.

from

"' xmlns='jabber:client' version='1.0' xmlns:stream='http://etherx.jabber.org/streams'>"]). 

to something like this

"' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'>"]). 
Profile