Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
Has anyone noticed problems with the handover URL and hash location strategy routing?
Our developers have a question around the specific details around how the redirect from Silanis to the handover URL is handled. Could someone shed some light onto what mechanism is used?
I'm seeing some odd behavior, on my local development environment, I can create a package and delete the "default-consent" page without issue.
Has anyone run into a Certificate chaining error when trying to make a call to createPackage?
What are the inbound IP addresses for eSignLive? And do these change with the new Sender UI (i.e. the new *.esignlive.com domain vs. *.e-signlive.com)?

Replies Created

Reply to: How to handle smaller text fields when viewing on a mobile device?

0 votes
Thanks for the suggestion, unfortunately it didn't seem to work in my case. I tried variations on the 40x30 size and still could not see the output on a few devices (iPhone 6, iPhone 6 Plus, Samsung S6) in both landscape and portrait orientation with both modes clipping some of the text that was entered. Here's an example code snippet: FieldValidator dateList = new FieldValidator(); exemptDate.setStyle(FieldStyle.UNBOUND_TEXT_FIELD); exemptDate.setPage(page); exemptDate.setX(418); exemptDate.setY(130); exemptDate.setHeight(30); exemptDate.setWidth(40); exemptDate.setId(new FieldId("exemptDate")); ... fields.add(exemptDate); signature.addFields(fields); doc.addSignatures(signatures); Is there some left/right justification flag that I might be missing? Here's my example (note - once the signature has been confirmed, all of the data is visible, however, while doing data entry it is clipped): https://sandbox.esignlive.com/auth?target=https%3A%2F%2Fsandbox.esignlive.com%2Fpackages%2F81004219-a8a6-4172-a002-9862e979904f%2Fsign&loginToken=Mi4xMDAwLlNSeHVYMERXTjVvPS5MeFVyZGpDakk0eFpRUzQ2TUlIWGtVZ3Arbmd2ZDhuczZFa21uaUJJR0RQL3RiRmhNSytNUklFbkYwSnM0RGtpeCt5TXI0eUdpZWs9 I've attached a couple of screenshots.

Attachments

Reply to: Minimum Java Version for Java SDK

1 votes
You can have a proxy in between your server and Silanis though, which can insulate you from the JDK 1.7 mandate (as long as your proxy supports the 2048 bit encryption).

Reply to: What IP Addresses to whitelist for communication to eSignLive?

2 votes
I forgot to mention - we're U.S. based. Your support team quickly responded (Thanks Arthur!) to my scramble to get a quick list for our integration testing, so I'm including the reply here: v11.0 Sandbox US: Environment URL: https://sandbox.esignlive.com Primary IP: 54.85.59.26 Secondary IP: 54.164.84.186 Outbound IP: 54.84.89.182 v10.13.3 Sandbox US: Environment URL: https://sandbox.e-signlive.com Primary IP : 54.84.132.241 Secondary backup IP : 54.85.54.201 Outbound IP: 54.84.89.182 v10.13.3 Production US: Environment URL: https://apps.e-signlive.com Primary IP : 54.85.79.26 Secondary backup IP: 54.85.78.62 Outbound IP : 54.85.128.97

Subscriptions

Topics Replies Freshness Views Users
Has anyone noticed problems with the handover URL and hash location strategy routing?
1 3 years 3 months ago 16
Our developers have a question around the specific details around how the redirect from Silanis to the handover URL is handled. Could someone shed some light onto what mechanism is used?
3 5 years 11 months ago 23
I'm seeing some odd behavior, on my local development environment, I can create a package and delete the "default-consent" page without issue.
3 6 years ago 6
Has anyone run into a Certificate chaining error when trying to make a call to createPackage?
2 5 years 11 months ago 1,205
What are the inbound IP addresses for eSignLive? And do these change with the new Sender UI (i.e. the new *.esignlive.com domain vs. *.e-signlive.com)?
4 4 years ago 215

Code Share

This user has not submitted any code shares.