While diagnosing some login problems in our server, we came across an issue with the OneTeam for iPhone client.  Specifically, when negotiating the “session” feature during stream initialization, the client is not including an “id” attribute on the IQ.  This is causing the server is then rejecting the request, which effectively prohibits the client from being used.

Regards,
Jack

Was this issue ever looked at?  Trying to connect to an account on jabber.com and wondering if this is my issue as well.

RFC 3920:
# The ‘id’ attribute is REQUIRED for IQ stanzas.

Does anyone know of any other issues with jabber.com or other corporate users of XCP servers?

This issue was solved long time.
We are not aware of any other problems.

Thank you for the quick reply.  Can I send you an account on jabber.com to try perhaps?  I get the Invalid JID error when I try to connect.

If you want but it had been checked by people at Cisco.

I am trying to use plain username/password iq:auth to authenticate with my local server:

<iq id=‘auth_1’ type=‘result’><query ><username>sk</username></query></iq>

The client is sending back <digest> auth even though it was not offered by the server:

<iq id=‘171b70001c6aaa’ type=‘set’><query ><username>sk</username><digest>2373FDFD727ECC27371A4363DBC9B3FDC3F3ACA4</digest><resource>ot</resource></query></iq>

I switch my server to offer <digest> iq:auth, but unfortunately it expects the hash to be all lower-case per XEP-78 (which the server should really be double-checking). 

Any chance there is a client flag to allow plain username/pw iq:auth?  I am currently unable to configure SASL unfortunately.  :)

Yes, we will fix capitalization on digest and add plain auth in next version.