?Hi @Ankur Sharma? ,
Yes definitely Chrome, I don't have safari.
Seems that after investigation and testing I found the issue.
I needed to exclusively allow cookies to be set for the site, just clicking on the allow cookies in the url locater wasn't enough. I needed to add a Wild card allow for the domain. See Attachment
You can replicate this by blocking cookies, remove any exclusive allows for domains and clear browser cache and load the page after restarting chrome and the safari error from the SSA code is triggered. As far as I can tell the error is triggered when the embedded SSA site cannot set its jsessionid. The demo site worked because I had whitelisted the site in the past.
Thanks for taking the time to look at this
Have a merry Christmas
cheers