I’'m using Wildfire 3.1.1 with LDAP integration.
All the clients I’'ve tried (Pandion, SoapBox, Spark, Exodus…) work great.
But there is this new .NET SoapBox Studio 2007 I’‘m considering using for some client development, but it’'s sample program cannot logon to my server.
I turned on debug tracing, and I see the issue, but I don’'t know if it is an issue with WildFire or the client library.
When the logon request arrives from the new Soapbox Studio 2007 client, it traces that it is looking for "email@example.com" in OU… So it seems to be sending the full JID as the userid in the connect request.
When I logon from Spark, WildFire debug traces that it is looking for “username” in OU…
Now, I also tried the Soapbox sample program against google talk, and it logged me on just fine. So perhaps this is either a “bug” or a “feature request” for LDAP logon requests that if the userid is passed in the form of a JID, that the userid portion of the JID be used when searching the LDAP database.
The Soapbox Studio is open source, but I haven’'t successfully built it from source yet, but when I do I can try to change it there if necessary.
What do you think? Is this a server issue or client? I don’'t know the XMPP spec enough to say…