Embedded signing URL generation
Tuesday, March 27, 2018 at 11:19amHi
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
Reply to: Embedded signing URL generation
Tuesday, March 27, 2018 at 11:42amReply to: Embedded signing URL generation
Tuesday, March 27, 2018 at 11:49am