topic Jabber API does not work with Internet Explorer in Cloud Collaboration

Jabber API does not work with Internet Explorer

mihir.shah.13 — Thu, 11 Jun 2015 06:12:27 GMT

When I try to authenticate a user by calling the following method in API version 8.6.1.28927, I get an error in the response saying Access Denied.

function ConnectUser() {

try {

debugger;

var arg = {

httpBindingURL: demo_config.httpBindingURL,

successCallback: function success() {

alert("connection successful");

SubscribeUsers();

this; //The client

errorCallback: function (err) {

debugger;

var tstr = jabberwerx.util.serializeXML(err);

jabberwerx.util.debug.warn(tstr);

alert("connection failed");

}

client.connect("mihir.shah.1349" + "@" + demo_config.domain, "cisco1234", arg);

} catch (ex) {

jabberwerx.util.debug.warn(ex.message);

jabberwerx.$("#log").text("Could not connect: " + ex.message);

}

This happens only when using Internet Explorer. It works fine with other browsers such as Chrome & Safari. Please help me resolve this issue

Re: Jabber API does not work with Internet Explorer

npetrele — Tue, 16 Jun 2015 15:21:04 GMT

What version of IE are you using? What version of Windows (and 32 or 64 bit)?

Re: Jabber API does not work with Internet Explorer

mihir.shah.13 — Wed, 17 Jun 2015 03:39:59 GMT

I tried with IE 10.0 & 11.0 on 64 bit systems

Thanks,

Beena

Re: Jabber API does not work with Internet Explorer

mihir.shah.13 — Wed, 17 Jun 2015 06:43:00 GMT

& Windows 7 OS

Re: Jabber API does not work with Internet Explorer

npetrele — Thu, 18 Jun 2015 17:31:44 GMT

I'm not sure I could diagnose your problem without seeing a lot more of your code and the configuration of your server.

I tried an old demo application on IE 11 on Windows 7 and it worked fine for me, so it's not an IE 11 compatibility problem.

Re: Jabber API does not work with Internet Explorer

mihir.shah.13 — Mon, 31 Aug 2015 05:28:17 GMT

Hi Nicholas,

Could you please point me to the ideal server configurations? I tried in two different networks & observed the same behavior. So, I am not able to compare the server configurations.

Thanks,

Beena