dejan_lukic7ho…

is this a bug?

0 votes
I'm using .Net SDK. I create token: string sessionTokenString = eslClient.AuthenticationTokenService.CreateSenderAuthenticationToken(id); and then

Reply to: is this a bug?

0 votes
Try using the "generatedLinkToPackageViewForSender" url from this as the source for your iframe, instead:
string senderAuthenticationToken = eslClient.AuthenticationTokenService.CreateSenderAuthenticationToken(packageId);
AuthenticationClient authenticationClient = new AuthenticationClient("https://sandbox.esignlive.com");
string generatedLinkToPackageViewForSender = authenticationClient.BuildRedirectToPackageViewForSender(senderAuthenticationToken, packageId);
Hope this helps. Let me know.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: is this a bug?

0 votes
This works in a sense that shows package information same as on sandbox site. It was working before like this. I could verify that draft package is created. The problem was to integrate this into our site. I don't want to see e-SignLive logo or navigation buttons. I want to go straight do a document or documents uploaded to create placeholder for signatures and then continue with workflow.

Reply to: is this a bug?

0 votes
If you want to use the URL that you've specified, you'll need to create a sessionToken:
eslClient.SessionService.CreateSessionToken(packageId, signer);

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off