Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Approved Answers
Replies
Preferences
Topic Started
This user has not created any forum posts.
Replies Created
Approved Answer
Reply to: How to connect integration code to SSL secured backend
Tuesday, April 5, 2016 at 07:24amIn order to run integration code (JAVA, .NET SDK…) targeting an SSL secured connection to the backend, one of the following steps is required.
1. If the backend is configured with a self-signed cert (standard configuration for DEV environment), then make sure to import the public key associated to the backend SSL cert and successfully install it in the trusted store of the machine running your framework code.
2. If the backend is configured with a CA signed cert like Verisign … (standard configuration for PROD environment), then make sure that either :
a. The root and intermediate cert associated to the backend SSL cert are successfully installed it in the trusted store of the machine running your framework code or
b. Import the public key associated to the backend SSL cert and successfully install it in the trusted store of the machine running your framework code.
Reply to: Certificate chaining error - WebSphere Application Server
Thursday, April 7, 2016 at 09:11amHi ,
I think you will need to check if you have the root and intermediate cert also imported in the default cell trust store, also make sure that you unset the JRE ca trust cert and restart the web-server.
This might help you fix the problem. Obviously during the handshake the WebSphere server where the SDK is used is not able to retrieve the trust cert from the defaults cell trust store and this can be caused by many reasons:
1. The user running the SDK does not have permission to retrieve the cert.
2. miss configuration of root , intermediate and signer cert each on the right place or anything else.
Again this is not an SDK problem rather than infra problem.
Kind regards,
Imane
Approved Answer
Reply to: Issue Changing Signature Type After Package Created
Thursday, May 18, 2017 at 06:21amThe following will allow you to change the the signature type after a transaction is already created:
DocumentPackage docpackage = eslClient.getPackage(packageId); Collectionsignatures = docpackage.getDocument("sampleAgreement").getSignatures(); Signature oldSignature = null; for (Signature s:signatures) { if ("Signature1".equals(s.getName())) { oldSignature = s; break; } } Signature signature = SignatureBuilder.captureFor("[email protected]") .withName("Signature1") .atPosition(oldSignature.getX(),oldSignature.getY()) .withSize(oldSignature.getWidth(),oldSignature.getHeight()) .build(); eslClient.getApprovalService().modifySignature(docpackage, "id", signature);
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
I'm experiencing an issue when I try to update a signature type from click-to-sign to capture, after a transaction is created.
We have tried the modifySignature method using the Java SDK and it seems
|
2 | 6 years 11 months ago | 14 | |
Has anyone run into a Certificate chaining error when trying to make a call to createPackage?
|
2 | 7 years 11 months ago | 1,481 | |
What is the recommended best practice to connect integration code to a SSL secured backend? Any help/guidance would be appreciated.
hsamson
|
2 | 8 years ago | 39 |
Subscriptions Release Notes
This user is not subscribed to any release notes.