X-Frame-Options sameorigin about amazon-connect-streams

[abearden]

And it figures, after asking for help the answer comes. The correct url is "https://domain.awsapps.com/connect/ccp#", the pound sign being vastly important for some reason.

[atekie]

I am receiving the same error even when using https://domain.awsapps.com/connect/ccp# (replacing domain with our actual domain) as the url. I am including the single js file built, plus I have whitelisted the domain. What am I missing?

[autrey]

@atekie Hopefully this isn't a stupid question, but did you whitelist the domain as https (which is required)?

[atekie]

@autrey yes we did whitelist the domain with https, thanks for chiming in!

[stupidasker]

we are facing same error , after doing every thing on amazon connect integration.

<title>Amazon Connect</title>

<script type="text/javascript" src="{{ asset('js/amazon-connect-v1.2.0.js') }}"></script> <script type="text/javascript"> connect.core.initCCP(containerDiv, { ccpUrl: 'https://INSTANCENAME.awsapps.com/connect/ccp#', loginPopup: true, softphone: { allowFramedSoftphone: true } }); </script>

[MercedesFiore]

I have the same intermittent issue.

Refused to display 'https://domain.awsapps.com/connect/login?landat=%2Fconnect%2Fccp#/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

connect.core.initCCP(containerDiv, { ccpUrl: 'https://domain.awsapps.com/connect/ccp#/', loginPopup: true, softphone: { disableRingtone: false, //ringtoneUrl: ringtoneUrl allowFramedSoftphone: true } });

As a work around, I've added a login button to the container div - which I hide when agent connects. This is pretty clunky. Looking for a better solution.

[sromocki]

I don't get this issue locally, but I do get this issue in a staging server that I've created.
The successful request, locally, looks like this:

The same request on the staging server where I get the 'sameorigin' error, looks like this:

The only difference I see is some cookie key/values missing: username=; lily-auth-prod-iad=;
Not sure why those get populated locally vs on the staging server.

[AshishYW]

hi ,

I am also facing same issue of X-Frame-Options' to 'sameorigin'
Is there any solution for th

[mschersten]

Not sure how relevant this is to all the different problems here, but make sure that you not only whitelisted the custom panel as https, but that you are also accessing it that way as well. I got lazy and tried to load s3.amazonaws.com/mybucket, without https, and from some computers is loads securely by default, others not.

[weynhamz]

Encountered this today while integrating with Salesforce, nearly given up, it turns out that need to add the Virualforce page domain used in CCP control panel to the Connect Approved origins list.

I have encountered the same issue and ended up resolving the issue by added https://XXXXXXXX--amazonconnect.ap1.visual.force.com/ to the Approved origins in the Application integration section of Amazon Connect.

[satyendragupta]

And it figures, after asking for help the answer comes. The correct url is "https://domain.awsapps.com/connect/ccp#", the pound sign being vastly important for some reaso

[old-square-eyes]

Still seems an issue in 2023. I followed the guide to the letter and it seems out of date. Browsing to my cloudfront address my browser has a fit with the SAME ORIGIN issue. Yes I have set the cloudfront address as an approved origin in Connect. It seems to get upset with the auth redirect url. I added that too for good measure. Do I have to add something in cloudfront? I'm not even sure why it's wanting me to auth. It does it if I'm already logged in too.