01-21-2020 04:48 AM
Finesse non-gadget sample working fine with Finesse v11.6 however, the same code doesn't work with Finesse v12.0.1.
getting below errors when signed-in (attached console log)
Errors are :
1) jquery-3.2.1.min.js:4 PUT http://localhost:70/finesse/api/User/Agent001 403 (Forbidden)
2) core-sys.js:801 Uncaught TypeError: Cannot read property 'status' of undefined
at _signInHandler (core-sys.js:801)
at Object.error (finessenongadget.js:59)
at i (jquery-3.2.1.min.js:2)
at Object.fireWith [as rejectWith] (jquery-3.2.1.min.js:2)
at A (jquery-3.2.1.min.js:4)
at XMLHttpRequest.<anonymous> (jquery-3.2.1.min.js:4)
Regards,
Sanmesh
01-21-2020 09:36 AM
Hi,
The non gadget sample was tested against 12.0 so it should work. I haven't tested it out myself though.
Did you manually try to log into the 12.0 system with the same URI and credentials to see if it is successful?
Did you take a look at the Finesse webservices and realm logs to see why you are getting a 403?
Thanx,
Denise
01-21-2020 09:29 PM
Did you manually try to log into the 12.0 system with the same URI and credentials to see if it is successful?
- Yes. It works and gives the XML Response as Sign-out
Access this url: http://localhost:70/finesse/api/User/Agent001 and received an XML Reponse :
Did you take a look at the Finesse webservices and realm logs to see why you are getting a 403?
- Do we need to check these logs on Cisco Finesse Server?
jquery-3.2.1.min.js:4 PUT http://localhost:70/finesse/api/User/Agent001 403 (Forbidden)
is the error.
is this problem regarding jquery? Do i need to use latest jquery?
01-21-2020 10:04 PM
The error that you pasted is from the client side. I am talking about the error from the server/realm side. Did you use the browser's debugger to confirm that the authentication is being sent? Is the authentication correct?
In your example of your trial, I believe you are doing a GET since you are getting a XML response back while the application is doing a PUT (per your logs).
Thanx,
Denise
01-21-2020 11:18 PM
description: Access to the specified resource has been forbidden.
01-22-2020 09:49 AM
Hi,
There is something wrong from the client side. It is not giving you a 401, so the credentials are probably ok.
Did you look at the Finesse webservices and realm logs?
Thanx,
Denise
01-24-2020 04:09 AM
01-24-2020 09:15 AM
01-27-2020 01:54 PM
Hi.
I think I saw in the DevNet support room that this issue is resolved. Can you confirm?
Thanx,
Denise
01-27-2020 09:30 PM
When I enabled_all (using CORS CLI command) for CORS then it started working but actually we want to add Origin and then it should work without enable_all. When we tired to add Origin using CLI command not able to add it is giving operation failed error.
We are using SANDBOX Lab 12.0.
Regards,
Pravin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide