iFrame in Chrome
Monday, March 6, 2017 at 05:59amWhen accessing a session URL, I can see that eSignLive returns a few 302s and the browser does some redirects. For whatever reason, Chrome cancels one of these redirects when it's in an iFrame (https://sandbox.e-signlive.com/packages/{packageId}/sign). This seems to result in eSignLive falling back on http://sandbox.e-signlive.com/login?destination=/packages/{packageId}/sign, and Chrome gets upset about the mixed-content.
Has anyone else encountered this problem and is there a solution? I don't expect this is specific to URLs generated from the Java SDK, but that's how I'm integrating.
Reply to: iFrame in Chrome
Monday, March 6, 2017 at 09:20amReply to: iFrame in Chrome
Monday, March 6, 2017 at 12:23pmReply to: iFrame in Chrome
Monday, March 6, 2017 at 01:12pmReply to: iFrame in Chrome
Tuesday, March 7, 2017 at 03:38amReply to: iFrame in Chrome
Tuesday, March 7, 2017 at 04:36amReply to: iFrame in Chrome
Monday, March 6, 2017 at 10:44amReply to: HeyjhullinIdidn
Tuesday, April 14, 2020 at 12:02pmHi, Williams, I also have the same issue. Can you provide a way about how to create session token with https://sandbox.e-signlive.com/access?sessionToken={sessionToken} ??