Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
Topics |
---|
Hi,
i have a problem when trying to generate a URL with sender authentication token to package view.
When i do that on old-instance (sandbox.e-signlive.ca) its working fine.
But when i do that on n
|
Hi,
i am trying to integrate our web application with e-signature and display the "package view" for sender in iframe.
What i CAN do and what is working is to obtain a session and build a package v
|
Replies Created
Reply to: Create a sender session to display just ONE package in package view
Thursday, October 6, 2016 at 04:16amHi Haris,
thanks for the response.
The very important thing for us is to "somehow" restrict the user to view all packages. Its like a "showstopper" for us.
We have an account and an account owner.
By default when you create a package (using java sdk) this account owner is set as a "sender" of this package (and also as an "auditor" of the package)
And there comes the problem.
There is one sender for thousands of different clients/organizations our IBM application is using!
So when i create a SENDER session token, generate the URL to view the package and display it in iframe - every one user of these thousands can freely browse every package created.
So we need to restrict it.
Possible options:
1) If in few months can e-signature implement method to restrict to view just ONE package that would be most awesome for us.
Something very similar to this:
String senderAuthenticationToken = eslClient.getAuthenticationTokensService().createSenderAuthenticationToken(packageId.getId());
String redirectToPackageViewForSender = authenticationClient.buildRedirectToPackageViewForSender(senderAuthenticationToken, packageId.getId());
2) Second option is not so elegant but is very easy to implement for esignature
Just give a sender (or creator of the pacakge) the option to configure the "package view" similar to the "designer" (usinig CeremonyLayoutSettingsBuilder)
So that sender can disable/hide to view the NAVIGATION buttons. (just hide the navigation div)
3) Third option is something what is doable right now but little complicated but does not require any modifications on esignature side
For every of our client/organization we will create a "sender" account under our account.
by calling: eslClient.getAccountService().inviteUser(...)
This will send an invitation email BUT also create a sender account and we can start using this sender account even without confirming it (so we can use unexisting email address like [email protected])
This approach would require to create maybe a thousands of sender accounts under our esingature accout.
So the question is. Is it OK to esignature to have a thousands of sender accounts under 1 account?
We will then set a "SenderInfo" for the DocumentPackage and create a session token and URL to view it inside the iframe.
And as i said, even the sender account (invitaion email) is not confirmed, the session is created and package can be viewed...
What do you think. What is doable for esignature or what would be the best for us? Is there any other possibility to do that?
Thanks.
Reply to: Create a sender session to display just ONE package in package view
Thursday, October 6, 2016 at 05:55amAllright, thats a great news for us. If we create a session token which will allows user/sender to view just one specified pacakge and prevent to see others (by stealing url etc) that would be terrific.
So basically the new designer will (from the functinality perspective) replace the package view and allows us to add signers, documents and modify the package in draft state?
Do you know when the new UI will be implemented on all instances (australia, canada, brazil,japan, etc... )
Thanks.
Tomas.
Reply to: Session token on NEW INSTANCE/UI is poining to OLD UI
Monday, November 7, 2016 at 04:18amThanks for info about the URL issue.
Regarding the document upload issue i found that it is document related.
For testing i am using documents from source file jar
http://docs.e-signlive.com/11.0/sdk/esl-sdk-java-11.0.zip
document-with-fields.pdf causing this error
extract_document.pdf failing too
document.pdf is working fine
document-for-anchor-extraction.pdf fine
document.odt fine
field_groups.pdf fine
AND what's more the signer of the package must be added after package is created:
here is complete code to reproduce the problem:
@Test public void testDocumentPackageSettings() { System.out.println("== testDocumentPackageSettings =="); String DECLINE_REASON_1 = "Decline reason One"; String DECLINE_REASON_2 = "Decline reason Two"; String DECLINE_REASON_3 = "Decline reason Three"; String OPT_OUT_REASON_1 = "Opt out reason One"; String OPT_OUT_REASON_2 = "Opt out reason Two"; String OPT_OUT_REASON_3 = "Opt out reason Three"; String HAND_OVER_LINK_HREF = "http://www.google.ca"; String HAND_OVER_LINK_TEXT = "click here"; String HAND_OVER_LINK_TOOLTIP = "link tooltip"; DocumentPackage superDuperPackage = PackageBuilder.newPackageNamed( "Custom " + new SimpleDateFormat( "HH:mm:ss" ).format( new Date() ) ) .withSettings( DocumentPackageSettingsBuilder.newDocumentPackageSettings() .withInPerson() .withoutLanguageDropDown() .hideOwnerInPersonDropDown() .disableFirstAffidavit() .disableSecondAffidavit() .withDecline() .withDeclineReason(DECLINE_REASON_1) .withDeclineReason(DECLINE_REASON_2) .withDeclineReason(DECLINE_REASON_3) .withOptOut() .withOptOutReason(OPT_OUT_REASON_1) .withOptOutReason(OPT_OUT_REASON_2) .withOptOutReason(OPT_OUT_REASON_3) .withHandOverLinkHref(HAND_OVER_LINK_HREF) .withHandOverLinkText(HAND_OVER_LINK_TEXT) .withHandOverLinkTooltip(HAND_OVER_LINK_TOOLTIP) .withDialogOnComplete() .withCeremonyLayoutSettings( CeremonyLayoutSettingsBuilder.newCeremonyLayoutSettings() .withoutGlobalConfirmButton() .withoutGlobalSaveAsLayoutButton() ) ) .build(); PackageId myPackageId = eslClient.createPackage( superDuperPackage ); System.out.println("myPackageId: " + myPackageId); Signer signer = SignerBuilder.newSignerWithEmail(SIGNER_FRST_EMAIL) .withFirstName(SIGNER_FRST_FIRST_NAME) .withLastName(SIGNER_FRST_LAST_NAME) .build(); superDuperPackage = eslClient.getPackage(myPackageId); eslClient.getPackageService().addSigner(superDuperPackage.getId(), signer); Document document = DocumentBuilder.newDocumentWithName("DOCUMENT_SETUP_NAME") .withDescription("TEST_DOC_FILE_NAME_DOC_PDF_STREAM") .fromStream( loadDocumentInputStream("document-with-fields.pdf"), DocumentType.PDF ) .build(); superDuperPackage = eslClient.getPackage(myPackageId); //Add document to the existing package document = eslClient.uploadDocument(document, superDuperPackage); System.out.println("== testDocumentPackageSettings PASSED =="); }Then failing line is in SignatureConverter.toSDKSignature:66 signatureBuilder is null NOTE: on the OLD instance its working fine Here is the full trace:
com.silanis.esl.sdk.EslException: Could not upload document to package. at com.silanis.esl.sdk.service.PackageService.uploadApiDocument(PackageService.java:257) at com.silanis.esl.sdk.service.PackageService.uploadDocument(PackageService.java:240) at com.silanis.esl.sdk.EslClient.uploadDocument(EslClient.java:564) at com.silanis.esl.sdk.EslClient.uploadDocument(EslClient.java:568) at com.ibm.pgms.esign.PackagesServiceSDKTest.testDocumentPackageSettings(PackagesServiceSDKTest.java:533) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.NullPointerException at com.silanis.esl.sdk.internal.converter.SignatureConverter.toSDKSignature(SignatureConverter.java:66) at com.silanis.esl.sdk.internal.converter.DocumentConverter.toSDKDocument(DocumentConverter.java:63) at com.silanis.esl.sdk.service.PackageService.uploadApiDocument(PackageService.java:253) ... 26 more
Reply to: Session token on NEW INSTANCE/UI is poining to OLD UI
Friday, November 11, 2016 at 03:38amsure as i said i am using document which are freely available in the source JAR file from that link *(just unzip the jar), i will attach 1 document which is failing when trying to execute code i mentioned in my previous post
Reply to: Session token on NEW INSTANCE/UI is poining to OLD UI
Monday, November 14, 2016 at 04:27amyes, its test document, but if that error happens in 2 test documents it means that it can happens even on real one.
The code i posted is from syntactic point of view correct and in fact 100% working fine on OLD instance (for every tested document)
What i am trying to say that on NEW instance there could be possible error for this "setup".
BUT - If you execute that code i've posted it ends with an error. At least on my SDK v11.0
And ofc the code you've posted is correct but still it's a workaround and i would like to be able to add documents and signers to package which already exists.
i am attaching also second document which is causing this error.
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Hi,
i have a problem when trying to generate a URL with sender authentication token to package view.
When i do that on old-instance (sandbox.e-signlive.ca) its working fine.
But when i do that on n
|
7 | 7 years 4 months ago | 14 | |
Hi,
i am trying to integrate our web application with e-signature and display the "package view" for sender in iframe.
What i CAN do and what is working is to obtain a session and build a package v
|
5 | 7 years 5 months ago | 21 |
Subscriptions Release Notes
This user is not subscribed to any release notes.