cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3300
Views
0
Helpful
14
Replies

How to modify CROS policy on finesse server

amfat2000
Level 1
Level 1

How to modify CROS policy on finesse server,

14 Replies 14

sameyada
Cisco Employee
Cisco Employee

Did you mean CORS policy .Please refer the guide for CLI commands utils finesse cors enable/disable.

Thanks, Could you please provide a link for this guide.

Hi,

 

Here is the link to the guide: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1201/Admin/guide/cfin_b_1201-administration-guide-release-1201/cfin_b_1201-administration-guide-release-1201_appendix_01111.html#reference_F298A59463A427B...

 

What version of Finesse are you using? This CLI was introduced recently, I believe 11.6(1) ES4. If you are using a version before this, CORS is enabled by default.

 

Thanx,

Denise

exactly I'm using version 11.6 which is not enabled. and  i need to enable them . would you please advise how to enable them in terms of PCCE. Below only available on finesse

utils.png

I already read, but could not able to run the commands for enabling CROS as they are not found in the command list which i shared with you in the snapshot. below commands depicted in the document you shared are not there

  • utils finesse cors enable_all

  • utils finesse cors enable

Hi,

 

What version of 11.6 do you have? This was added in ES4. Do you have ES4 installed? If not, then CORS should automatically be enabled.

 

Thanx,

Denise

We have been advised by Cisco sales team to use PCCE sandbox to complete our development till finalize deployemnt. So i'm talking about the unique sandbox availed on Cisco Devnet PCCE 11.6. 

https://devnetsandbox.cisco.com/RM/Diagram/Index/69665078-12ff-4461-8f54-90ed161e5d72 

Hi,

 

That is actually version 11.5, so the CORS should automatically be enabled. You do not have to run the CLI for it.

 

Thanx,

Denise

well but i'm still getting below error

Access to XMLHttpRequest at 'https://fin-pub-a-50.berlin.icm:7443/http-bind' from origin 'https://fin-pub-a-50.berlin.icm:8445' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.

error.png

Hi,

 

Did you make sure to set the Origin header correctly?

cors.png

I see an error in your screenshot that says "Refused to set unsafe header "Origin"". If you are setting it, you need to look into why it is giving that error.

 

Thanx,

Denise

I intervened manually in the code to set origin but later discovered that it should be put by the browser and i should not intervene manually.

Now i uncomment the origin setting and it gave same error. Note that same finesse sample code was working fine with UCCX

error.png

Hi

I commented setting origin in the code as it should be set by browser and still getting same error. Please note that the CORS policy is enabled on UCCX sandbox and error not appearing there.

 

Hi,
I was also facing this issue for UCCX 11.6 I and tried to set the origin through the request Header in ajax but it didn't work as sending "Origin" as headers in ajax is not allowed.

Here's how I solved it,
I sent a request with Origin Header through postman. Here's the curl:

curl --location --request POST 'https://hq-uccx.abc.inc:7443/http-bind/' \
--header 'Origin: https://your.website.com' \
--header 'Content-Type: text/plain' \
--data-raw '<body xmlns="http://jabber.org/protocol/httpbind" xml:lang="en-GB" xmlns:xmpp="urn:xmpp:xbosh" hold="1" ver="1.9" to="abc.inc" wait="30" xmpp:version="1.0" from="Agent003@abc.inc" rid="1689702438"/>'

The postman is not restricted when sending the "Origin" as header, Once the origin is set, the finesse server will allow the request from the mentioned endpoint. And you're good to go.

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: