Hi, I realize that user experience with XMPP legacy networks transports as currently standardized and implemented is far from perfect and now I see that Openfire IM Gateway does not support external servers and implementing it would take more time than I am able to invest.
My motivation is to use Google Talk client because of its unique features, especially one thing I call “zero network configuration” and ability to run under “User” group account on windows. I can tell to my friends and family, who are really ordinary users and don’t know and don’t need to know what proxy or IP is, just to grab Google Talk client and install it or even take file I sent, drag it on desktop, double click it, enter ID and paswword and it works.
It works seamlessly even in corporate environment, where the only way out is ISA http proxy server requiring NTLM authentication. And this is because, according to my observations and knowledge, Google Talk client is able to:
Autodetect proxy host and port
Authenticate with proxy using NTLM.
Take credentials from windows session using SSPI or what is the correct name for this.
Adjust login server settings since it is necessary to connect to 443
If there exists another Jabber client working like this and Openfire can be configured to accept HTTP CONNECT connections on 443 port through proxy servers, then using my Openfire instance could be a solution, otherwise I will probably use jabberd, I expect C application will be more resource friendly, and PyICQt/PyAIMt.
But I have found no such client so far, I have tried close to dozen of them, but none work that way. In better case client can do NTLM, but have to be configured manually. And navigating normal user by phone or e-mail to find out and use correct configuration is quite a big problem, user would have to remember to change their passwords and if not, they risk locking their accounts.
In worse case clients do not support NTLM, so some other software like Python and NTLM APS or CNTLM must be used (this is case of original ICQ 6 client). This what I call bad user experience. But I was focusing primarily on multiprotocol clients, so pure Jabber client with this functionality still may exist.