Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
We're looking to help guide our customers through the signing process and it would be helpful if there was a mechanism that could help identify where they are as they transition from document to docum
We're looking to whitelist all possible eSignLive IP addresses for the notification events that we will receive for our packages.
Years ago, with our initial eSign implementation we noticed a significant drop off when we required a married couple to sign separately.
I have a particular document/form that has a few different fields which are of a small size, namely: date, year and state.

Replies Created

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

0 votes
Could someone share the IP addresses for the v11 U.S. servers? For both Production and Preview? Specifically I'd like to fill in the values for the backup IP and the Outbound IP sections: v11 Production US: Environment URL: https://apps.esignlive.com Primary IP: 52.4.146.88 Secondary backup IP: ? Outbound IP: ? v11 Preview US: Environment URL: https://preview.esignlive.com Primary IP: 54.165.234.57 Secondary backup IP: ? Outbound IP: ?

Reply to: Certificate chaining error - WebSphere Application Server

0 votes
In case this saves anyone some time, here are the two things that I found that caused me a huge headache: 1) The version of StringEntity available to me in WebSphere was older and did not have the method StringEntity(String, Charset) 2) The buildHttpClient() call in RestClient.java was unfriendly to WebSphere, it defaulted to using the Java cacerts store instead of WebSphere's default trust store, which caused issues when we had our various security appliances put into play. I ended up creating my own versions of EslClient.java and RestClient.java. EslClient.java changes were only necessary to use my custom version of RestClient. To get around method not found / classpath issues with #1 above, I used the older/available version of StringEntity:
StringEntity body = new StringEntity(jsonPayload, CHARSET_UTF_8);
            vs
StringEntity body = new StringEntity(jsonPayload, Charset.forName("UTF-8"));
And to use the WebSphere default Trust Store, I ended up adding the simple line .useSystemProperties() to the HttpClients.custom() call in RestClient.java's buildHttpClient(). I won't tell you how long that took me to find! Still looking at alternatives, as RestClient.java is an internal file for the Silanis SDK and I'd rather avoid making changes to the underlying SDK.
private CloseableHttpClient buildHttpClient() throws HttpException {
        final HttpClientBuilder httpClientBuilder = HttpClients.custom().useSystemProperties();

Reply to: Handover URL details about the redirect

0 votes
We're looking for how the contents of the iframe are redirected. Is it by doing setting iframe.src, window.location, 302 redirect, or some other method?

Subscriptions

Topics Replies Freshness Views Users
We're looking to help guide our customers through the signing process and it would be helpful if there was a mechanism that could help identify where they are as they transition from document to docum
2 8 years ago 30
Profile picture for user mwilliams
We're looking to whitelist all possible eSignLive IP addresses for the notification events that we will receive for our packages.
3 8 years 1 month ago 70
Profile picture for user harishaidary
Years ago, with our initial eSign implementation we noticed a significant drop off when we required a married couple to sign separately.
2 8 years 2 months ago 20
Profile picture for user harishaidary
Profile picture for user fperrault
What is the minimum Java version required for the Java SDK?
4 8 years 2 months ago 37
I have a particular document/form that has a few different fields which are of a small size, namely: date, year and state.
5 8 years 2 months ago 29
Profile picture for user harishaidary

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.