Finesse nongadget sample 10.5.1 problem with sandbox UCCX lab

[chapelain36]

Hi, all.I am trying to use NonGadget 10.5(1) sample with UCCX lab.

Non gadget sample there is located on local web-server. I tried to do this from 10.10.20.120 - with the same result.

When I am trying to sign in - I get an error in response:

XMLHttpRequest cannot load https://hq-uccx.abc.inc:8445/finesse/api/User/Agent001. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:81' is therefore not allowed access.

Requests are here:

What could be the reason of such behaviour?

I guess - something wrong with response? And header 'Access-Control-Allow-Origin' is missing?

With regards, Yuriy.

[dekwan]

Hi,

There have been a few people reporting issues on the NonGadgetSample with the later versions of Finesse/browsers. I am currently looking into these issues.

Which browser are you using? From the User-Agent, I see Chrome? This NonGadgetSample has only been tested with a very old version of firefox, but I'm able to sign in with FF 38 ESR.

If you are indeed using Chrome, please try using FF. If not, stay put as I am looking into the non gadget sample as a whole.

Thanx,

Denise

[chapelain36]

Hi, Denise.

I tried FF, IE and Chrome. The same result.

With regards, Yuriy.

[dekwan]

Hi,

I think there are some SSL issues using the https REST APIs on the sandbox. Can you try using the http REST API? That would be http://hq-uccx.abc.inc:8082/finesse/api/User/Agent001.

Also, double check your proxy to make sure it is configured correctly. Lastly, it is always a good idea to use Poster or Postman to call these REST APIs directly to make sure they are working as expected.

Thanx,

Denise

[chapelain36]

I can access this url directly, but when I am doing it from js - it seems just need CORS header "Access-Control-Allow-Origin"
to be included in the response, it is required by security reasons, cause my localhost is in other domain.

At my web server I just added

     <httpProtocol>

     <customHeaders>

       <add name="Access-Control-Allow-Origin" value="*" />

       <add name="Access-Control-Allow-Methods" value="GET,PUT,POST,DELETE,OPTIONS" />

       <add name="Access-Control-Allow-Headers" value="Content-Type" />  

     </customHeaders>

   </httpProtocol>

into the web.config - and it solves similar problem.
Is there a way to include this header in the response? It looks like nesessary for development and debugging.

With regards, Yuriy.

[dekwan · Accepted solution]

Unfortunately, Finesse currently does not support CORS. I do not know of a way to include those in the header.

[Astaroth_666]

Hi,

hitting the same wall today ... Any idea when it will be fixed?

First I tried this: http://www.html5rocks.com/en/tutorials/cors/#toc-adding-cors-support-to-the-server

but after about one hour trying to solve the problem I decided to take a closer look into the forum ... I should have this earlier.

Anyway, is there a chance to get a solution soon?

Cheers

Patrick

[Astaroth_666]

Well, as far as I can see somebody opened a bug:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv28419/?referring_site=bugquickviewredir

[dekwan]

Hi Patrick,

CORS support will be available in the upcoming release of 11.5. The exact date of the release is not concrete at this time, but it should be within a couple of months.

Thanx,

Denise

[Astaroth_666]

Hi Denise,

thanks for the quick reply.

But as far as I understood, it is also possible to use BOSH instead of XMLHttpRequest?

Cheers

Patrick

[dekwan]

Hi Patrick,

Correct. You can use BOSH.

Take a look at these pages of the developer guide: https://developer.cisco.com/media/finesseDevGuide3/CFIN_RF_M692B5FE_00_managing-notifications-in-third-party-apps.html

https://developer.cisco.com/media/finesseDevGuide3/CFIN_RF_IF8A5AA1_00_initializing-the-bosh-connection.html

Thanx,

Denise