jhullin's account

Thanks for following up on your own question. This should save me some time.

Try adding this when building your package:

.withSettings(DocumentPackageSettingsBuilder.newDocumentPackageSettings().hideOwnerInPersonDropDown())

Both methods of generating a URL have the same issue. And yes, it looks like it's a cookie issue. I noticed Chrome ships with the "Block third-party cookies" checked. I cleared that box and it worked. Given this is a common default security setting in at least a couple of browsers, do most customers avoid using eSignLive in an iFrame? I see a recent post about using a pop-up window to set a cookie before using an iFrame (Safari), but pop-ups are typically blocked as well.

I've tried a few ways of generating the URL through the SDK. Here's an example (should be good to go for the next 28 minutes).

    Test iframe    

I gave the latest SDK a try. I tried with two different sandbox accounts and two API URLs (with and without the hyphen). No luck.