Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
Topics |
---|
Hi,
We've discovered some behaviour that seems strange/inconsistent to our team.
|
Hi,
I am wondering if there's a back-office setting or configuration option that would force a signer to explicitly sign in every signature box instead of the current behavior - which is to collect t
|
Hi,
This forum has been such a great help so far, that I figured I'd post here on the off-chance you can provide some guidance.
We're working on displaying the Signing Ceremony iFrame within our app
|
Hi,
With the default security settings on Safari "Allow from Current Website Only", our application is unable to open either the designer or signing ceremony windows in an iframe.
|
Replies Created
Reply to: question about locked signers and in-person signing
Tuesday, March 14, 2017 at 10:42amHi Michael,
Thanks (as always) for the quick response. I agree that the existing behavior does make sense from a workflow perspective, but I found it strange that even if I open the iFrame using "Signer 2" (as opposed to the package owner) and switch to "Signer 1" (who's locked), I can still sign. So it's not making any decision based on my position as the package owner. I guess I expected switching signers to perform the equivalent action of changing the owner of the session token.
So either opening as "Signer 1" should assume that I'm in-person so it's ok to sign, or switching to "Signer 1" should recognize that I'm locked and continue to keep me locked out. It seems inconsistent.
Appreciate you offering to check with some other folks today. Please let me know when you've confirmed this.
Cheers,
-Chris
Reply to: Components in Layout moving after applying to other documents
Wednesday, March 15, 2017 at 08:01amOn closer investigation, it looks like it's not the signature boxes that are moving, but somehow the document is changing. I've attached an image of the two files compared side-by-side. The image on the left is the document that was used to create the layout, and the document on the right is the result of applying the layout to the document.
The process would be that we create and save the layout for the first document (the one on the left) and then apply that layout to other documents later in the workflow.
I've examined both documents in Word, and they appear to be identical - which they should be, it's essentially the same file saved under two different names.
Both images are from iframe in our application that's used to manage layouts.
Reply to: Removing a partially signed document from a transaction
Tuesday, March 28, 2017 at 02:32pmHi Haris,
I mentioned this post to some eSignLive folks today and they asked if there was a salesforce ticket number for the case? I guess they're looking to cross-reference this issue with others that we've raised. We're just trying to ensure that it's fixed in Sandbox so that we can continue development as well as ensure that it doesn't get pushed to prod in the next release.
Thanks,
-Chris
Reply to: Can you open a signing ceremony as the package owner when not a signer?
Tuesday, June 6, 2017 at 08:52amHi Haris,
I actually tried this earlier, but was unable to get it to work either. When I try to open the iframe using your code snippet, I get the following error:
06/06/2017 14:44:08.247 [tomcat-http--47] ERROR Unable to send for signing for package with ID=19233: Could not create a signer authentication token. Exception: HTTP POST on URI https://sandbox.esignlive.com/api/authenticationTokens/signer/multiUse resulted in response with status code: [500, Internal Server Error]. Optional details: {"technical":"No signer found with uid or email kN0SY1xrlDYZ","messageKey":"error.internal.default","code":500,"name":"Unhandled Server Error","message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team."}
com.silanis.esl.sdk.internal.EslServerException: Could not create a signer authentication token. Exception: HTTP POST on URI https://sandbox.esignlive.com/api/authenticationTokens/signer/multiUse resulted in response with status code: [500, Internal Server Error]. Optional details: {"technical":"No signer found with uid or email kN0SY1xrlDYZ","messageKey":"error.internal.default","code":500,"name":"Unhandled Server Error","message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team."}
at com.silanis.esl.sdk.service.apiclient.AuthenticationTokensApiClient.createSignerAuthenticationToken(AuthenticationTokensApiClient.java:72)
at com.silanis.esl.sdk.service.AuthenticationTokensService.createSignerAuthenticationToken(AuthenticationTokensService.java:70)
at com.silanis.esl.sdk.service.AuthenticationTokensService.createSignerAuthenticationToken(AuthenticationTokensService.java:56)
at com.pointclickcare.esignature.service.ESignatureServiceImpl.createSigningCeremonyUrlForPackage(ESignatureServiceImpl.java:568)
at com.pointclickcare.documentmanager.service.DocumentManagerEslServiceImpl.startSigningCeremonyFromPackageVO(DocumentManagerEslServiceImpl.java:168)
at com.pointclickcare.documentmanager.service.DocumentManagerServiceImpl.eSignAndCompleteDocument(DocumentManagerServiceImpl.java:516)
at com.pointclickcare.mvc.documentmanager.web.controllers.ClientDocumentListController.eSignAndComplete(ClientDocumentListController.java:471)
at com.pointclickcare.mvc.documentmanager.web.controllers.ClientDocumentListController.adminESignAndComplete(ClientDocumentListController.java:294)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.springsource.loaded.ri.ReflectiveInterceptor.jlrMethodInvoke(ReflectiveInterceptor.java:1426)
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at esolutions.PasswordExpirationFilter.doFilter(PasswordExpirationFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.pointclickcare.core.servlet.PCCClickjackFilter.doFilter(PCCClickjackFilter.java:28)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:130)
at com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.pointclickcare.core.web.UIContextFilter.doFilter(UIContextFilter.java:45)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.pointclickcare.core.communication.web.UserCommunicationFilter.doFilter(UserCommunicationFilter.java:159)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at esolutions.framework.controller.UserSessionManagerFilter.doFilter(UserSessionManagerFilter.java:70)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at fr.xebia.servlet.filter.ExpiresFilter.doFilter(ExpiresFilter.java:1243)
at com.pointclickcare.core.web.cache.PCCExpiresFilter.doFilter(PCCExpiresFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.silanis.esl.sdk.internal.RequestException: HTTP POST on URI https://sandbox.esignlive.com/api/authenticationTokens/signer/multiUse resulted in response with status code: [500, Internal Server Error]. Optional details: {"technical":"No signer found with uid or email kN0SY1xrlDYZ","messageKey":"error.internal.default","code":500,"name":"Unhandled Server Error","message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team."}
at com.silanis.esl.sdk.internal.RestClient.execute(RestClient.java:192)
at com.silanis.esl.sdk.internal.RestClient.post(RestClient.java:105)
at com.silanis.esl.sdk.service.apiclient.AuthenticationTokensApiClient.createSignerAuthenticationToken(AuthenticationTokensApiClient.java:69)
... 67 more
This is the same error that I receive if I obtain the URL via the authClient.buildRedirectToSigningForSigner() method while handing in a token for a signer with signatures instead of the sender (who as I mentioned has no signatures in the package).
When I check the sender's ID in the debugger, it matches the one in the error message. The error seems to imply that since the sender isn't a signer, I'm not able to open the package.
Finally, I can't be positive, but I believe that we used to use the approach that you recommended to open the signing ceremony as the package owner. I didn't mention it though because I can't remember if the sender was also a signer in those scenarios in the past. We're using 11.0.2 of the SDK now, but were using an older version (11.0) back then - if that helps.
Thanks for the quick response!
Cheers,
-Chris
Reply to: Can you open a signing ceremony as the package owner when not a signer?
Tuesday, June 6, 2017 at 09:21amHi Haris,
Your code worked like a charm!
Here's the code I was using:
String signerId = docPackage.getSigners().get(0).getId();
String signerAuthenticationToken = eslClient.getAuthenticationTokensService().createSignerAuthenticationToken(docPackage.getId().getId(), signerId);
String url = eSignatureConfigurationService.getEsignatureBaseUrl() + "/access?sessionToken=" + signerAuthenticationToken;
docPackage.getSigners().get(0).getId() was returning a different ID than packageService.getRoles().getSigners().get(0).getId();
For our signers, those IDs are the same (presumably because we set the customID for signers), but for the sender, those IDs don't match.
Thanks so much for your help - I'd have probably spent the whole day figuring out that on my own.
Cheers,
-Chris
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Hi,
Bit of an intermittent issue that we've run into on a production server, but we haven't been able to figure out the cause.
We have a document that's about 2 pages long, and it's used to create a
|
2 | 7 years 2 months ago | 13 | |
Hi,
We've discovered some behaviour that seems strange/inconsistent to our team.
|
3 | 7 years 2 months ago | 56 | |
Hi,
I am wondering if there's a back-office setting or configuration option that would force a signer to explicitly sign in every signature box instead of the current behavior - which is to collect t
|
5 | 7 years 1 month ago | 18 | |
Hi,
This forum has been such a great help so far, that I figured I'd post here on the off-chance you can provide some guidance.
We're working on displaying the Signing Ceremony iFrame within our app
|
16 | 6 years 5 months ago | 115 | |
Hi,
With the default security settings on Safari "Allow from Current Website Only", our application is unable to open either the designer or signing ceremony windows in an iframe.
|
13 | 4 years 6 months ago | 1,864 |
Subscriptions Release Notes
This user is not subscribed to any release notes.