1 Answer
- Newest
- Most votes
- Most comments
0
Make sure in your initCCP options, you enabled loginPopup: true and loginPopupAutoClose: true
Assuming you have both of those, add
window.localStorage.removeItem('connectPopupManager::connect::loginPopup');
after your instanceURL declaration and before your function initialization, and make sure popups are enabled in your browser. The expected behavior is that initially you'll see the "refused to display" error, but it will then pop-up to your login provider, and after login, the pop-up window will close, and CCP will display.
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked a year ago
- asked 10 months ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 21 days ago
Thank You so much for replying.
The kind of behavior I am expecting that there should be no Login Popup Window at all.
When the user enters the URL in the browser, the login page must be displayed first.
After that, when the user enters the credentials, then the CCP window must be displayed.
In order to access the Amazon Connect CCP (Contact Control panel), the user must not be required to login to the Amazon Connect Dashboard.
You could accomplish something like this utilizing SSO, but the above steps would still be required in order to allow assertions to be passed to CCP to authorize the user. The x-frame-options SAMEORIGIN header blocks the authorization process from occurring within an iframe. In the event that the user is already logged in, the login window will pop up and use the existing session, then close the pop-up and proceed with loading the streams-based CCP