ADD non-existent users with openfire

Hi everybody!

We have the following problem, please any suggestion will be welcomed!

We are using Pandion clients; if we try to add an user that does not exist in Openfire Server (integrated with Active Directory), Openfire Server replies with: error code=“500”, but Pandion client adds the user to the roster anyway with status=“waiting for Authorization”

Here you have entire conversation: between Pandion and Openfire:

SENT: <iq type=“set” id=“sd20”><query xmlns=“jabber:iq:roster”><item jid="ppeee@begar.es"/></query></iq>

RECV: <iq type=“set” id=“204-152” to="jjalonso@begar.es/Mensajeria Interna de Begar, Powered by Pandion"><query xmlns=“jabber:iq:roster”><item jid="ppeee@begar.es" subscription=“none”></item></query></iq>

SENT: <iq type=“get” id=“sd21” to="ppeee@begar.es"><vCard xmlns=“vcard-temp”/></iq>

RECV: <iq type=“result” id=“sd20” to="jjalonso@begar.es/Mensajeria Interna de Begar, Powered by Pandion"></iq>

SENT: <presence type=“subscribe” to="ppeee@begar.es"/>

RECV: <iq type=“error” id=“sd21” from="ppeee@begar.es" to="jjalonso@begar.es/Mensajeria Interna de Begar, Powered by Pandion"><vCard xmlns=“vcard-temp”></vCard><error code=“500” type=“wait”><internal-server-error xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”></internal-server-error>&l t;/error></iq>

RECV: <iq type=“set” id=“451-153” to="jjalonso@begar.es/Mensajeria Interna de Begar, Powered by Pandion"><query xmlns=“jabber:iq:roster”><item jid="ppeee@begar.es" ask=“subscribe” subscription=“none”></item></query></iq>

SENT: <iq type=“get” id=“sd22” to="ppeee@begar.es"><vCard xmlns=“vcard-temp”/></iq>

RECV: <iq type=“error” id=“sd22” from="ppeee@begar.es" to="jjalonso@begar.es/Mensajeria Interna de Begar, Powered by Pandion"><vCard xmlns=“vcard-temp”></vCard><error code=“500” type=“wait”><internal-server-error xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas”></internal-server-error>&l t;/error></iq>

Versions:

Pandion 2.6

Openfire 3.4.1

Any help would be very appreciated.

Regards,

JJ.-

from the rfc:

o – the server could not process the

stanza because of a misconfiguration or an otherwise-undefined

internal server error; the associated error type SHOULD be “wait”.

so this looks like how this client handles these errors.

If the error type was cancel, prehaps then the adding would have failed.