FredericDH

Embedded signing URL generation

0 votes
Hi I have been playing with embedded signing URL generations lately and originally learned from this blog post that " Once you’ve gotten an authentication token, the next step is to build the following URL to embed in the src of your iframe" So I did the following : SessionToken signerToken = EslClient.CreateSignerSessionToken(package.Id,signer.Id); string url =$"{eSignLiveUrl}/access?sessionToken={signerToken.Token}"; The above code will give a URL looking as below : https://sandbox.esignlive.com/access?sessionToken=****TOKEN*** However, when looking at the SDK functions, I found this function that returns a similar url and that will point to the same signing ceremony for the given signer : AuthenticationClient authenticationClient =new AuthenticationClient(eSignLiveUrl); string Url = authenticationClient.BuildRedirectToSigningForSigner( signerToken.Token,package.Id); https://sandbox.esignlive.com/auth?signerAuthenticationToken=****TOKEN****&target=https%3a%2f%2fsandbox.esignlive.com%2fpackages%***PACKAGEID%3d%2fsign Can I safely assume the both codes are interchangeable ? Is the first method recommended in the blog post really the only method to use ? Thanks

Approved Answer

Reply to: Embedded signing URL generation

1 votes
Hi there, Yes both are indeed interchangeable. I would suggest using the first method since you don't really need to build another client to get url for the signing session.
Haris Haidary OneSpan Technical Consultant

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