path forward needed:

[jdickinson]

I have created a front end angular app that will fit as a third party application into finesse (gadget).

I am able to communicate with the api I built specifically for getting and updating our internal database.

I only get errors when calling the API that sits on the finesse server (even with SystemInfo call).

Is there a sample web-api that communicates with finesse that I can route through to make these calls to the finesse API.

Keep in mind, this is programming, POSTMAN does not mimic an rx/js call because there is no browser origin.

Joe

[jdickinson]

So the error is definitely at the API.

https://aboutssl.org/fix-google-chrome-error-err_ssl_protocol_error

sample code at:

https://github.com/foxjazz/finesseSandboxGadget.git

[dekwan]

Hi Joe,

Finesse 10.6 does not support CORS and therefore does not support the browser origin header. CORS support was not added until Finesse 11.5.

I am not familiar with using angular so I cannot comment on how to use the APIs using this language.

Thanx,

Denise

[jdickinson]

Hi all support people and Jacob...

I did a mental review over the weekend and while my sandbox is now expired I can explain why the api wasn't working.

It's simply this:  while the desktop gadget is installed, it only allows ssl traffic. The api however isn't setup to use ssl, if it were, your tutorials would have https instead of http as the main source of traffic.

Thought I would mention that because of our plans to set this up over the next couple of weeks for reals.

Thanks,

Joe

[dekwan · Accepted solution]

Hi Joe,

The api however isn't setup to use ssl, if it were, your tutorials would have https instead of http as the main source of traffic.

That is actually incorrect. The Finesse API works for both http and https. If you are trying to use https, you have to use the port 8445.

Thanx,

Denise

[jdickinson]

I tried this today and the postman worked with https, but the app embedded inside the gadget through a cors error which is odd since the domain and port I am plugged into is the same one I am calling in the gadget.

Same domain means no cross domain activity. So I think it's upset and sending the wrong message.

I am hoping this issue will resolve itself on 11.5 version.

[jankimehta]

I found the latest article about ERR_SSL_PROTOCOL_ERROR Chrome from Google.