AMAZON CONNECT ISSUE

[stupidasker]

REFUSED TO DISPLAY ..... IN A FRAME BECAUSE IT SET X-FRAME-OPTIONS TO SAMEORIGIN

ACK_TIMEOUT OCCURRED, ATTEMPTING TO POP THE LOGIN PAGE IF NOT ALREADY OPEN

OUR CONFIGURATION 👍

<title>Amazone 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>

[sromocki]

You can try to increase the load timeout. I got mine at ccpLoadTimeout: 25000.
Also, have you whitelisted your development hostname in whatever instance your working with.

[sromocki]

Also, I use Amazon's login page in an iFrame and don't use the loginPopup since I think it's better for my users. Maybe you desire the same functionality. "loginPopup: false"

[sromocki]

Also, as a crappy workaround, you can use this chrome extension https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe?hl=en-US

[ninjamike54]

If you're seeing X-Frame-Options errors, the solution depends on what page in particular is throwing errors:

If the page is *.awsapps.com/connect/ccp, you'll need to whitelist your domain (see https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-instance.html#app-integration for details on how to do this)
If the page is *.awsapps/connect/login, this means that you aren't yet signed in (we don't support framing any page other than the CCP, including the login page), signing in with the login popup should fix the issue, since the integration automatically refreshes the frame.

[snapshotleisure]

I got stung by this for a while, make sure your origin url is https if its not. Just something to double check

[snapshotleisure]

Hi, actually im having an issue similar to above, I have added my development domain to the whitelist, "https://localhost:4200". however the iframe won't load the Login Page (loginPopup:false), i get the X-Frame-Options error.

If I set loginPopup: true, and login using the new tab, it works fine. Is there a reason why the connect/cpp# url is not working with the whitelist? Is it something i'm missing? any help will be greatly appreciated.

Thanks

[alxx]

I'm using https, correctly provisioned in the Connect instance, I've tried both URLs (with /ccp and with /login), I've tried authenticating in the separate CCP, and nothing works. Whatever I do, I get "Refused to display '' in a frame because it set 'X-Frame-Options' to 'sameorigin'".

I understand that the iframe method is supposed to be phased out, but the latest version of the JS library still creates it.

Any suggestions?

[alxx]

After much googling I've found the problem: the correct URL should end in "/ccp#" with the pound making all the difference.
Why this isn't documented clearly, in bold red characters, is beyond me. I've been using the "/login" URL because that's the one I see in the Connect dashboard.

[anthonywebb]

Why allow loginPopup to be set to false if it literally does not work due to this cross domain issues.... SMH... Cmon, fix it or remove it, but dont waste the developers time trying to debug it.

[jagadeeshaby]

Please feel free to reopen if the issue persists.

More details can be found here - https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-instance.html#app-integration