getSignerURL - Unauthorized Access

Hi Peter,

(1)The default email template is so called "email.activate", while the manually triggered one is called "email.notify". Hence you may want to contact support team and disable the "email.activate" template.

(2)If you want to manually trigger the "email.notify", you can find the sample function from Resending a Signing Invitation guide.

Duo

Thank you! Do you have thoughts on why the getSignerURL takes me to a page that says "Unauthorized Access: Failed to get token". See attached and here is the link:

https://sandbox.esignlive.com/authentication?target=https%3A%2F%2Fsandbox.esignlive.com%2Ftransaction%2F4okpovYBFr9iPArj-YHUddV1qvo%3D%2Fsign&loginToken=NTkwTWJENGMyOTNIZE9KaVJqcG1La1Y2K2pMZWNadUJEem1UMzdGTmVVQUVqeEZFNjZyRURPZWg1OXp5cnMxNkVUb1R1bGR3VDhTTTArVk9OeUtRNUlWci8yL3hMTEEwOGFZTTJYRldLRGtidDYrZVorVXZoTWZDVW5TSzQrZzRlRTVKWWtkMVpVTjFVMmhyY1VRemEzTk5SMDFLV1VRek5USkJRbmhoWjFsdVpHZDFSM0J1UmpoRmJuVjNiWFozYVVkd1NIQmxla2xrTkZOMlZGcE9SOU9JTDUrYysvRGFM

Hi Peter,

Here's a testing signing URL:

https://sandbox.esignlive.com/authentication?target=https%3A%2F%2Fsandbox.esignlive.com%2Ftransaction%2FdccPVEwDXECx_nNDPBqGSA358hU%3D%2Fsign&loginToken=V2NvMXRPaFUxNmduSXJHY2ZWdmZGVkZNU1ZXWkVLNkJyOHo2NWE2VjM2eHdubXhNQXgvRjlZL0JPS2VZWTEyM1NHTWFHMEJ4VGxCdWNmRVQzc2ZLL0dpT29NU1pQWUw1eGRnZjIvUis5QlRGOXFIUkI1bWpRQ0VYVkVzYzdXWndVRFpxTjIxdmNVUm5aazgzZHprMVprOU9ZbVo2Y1RNM1lXZFlkWFZOYlZKbFFrNWtjV1Y0V25reWJqaFBOMGd5VldkWFNISnhZVXQwTW1rNGRHTTBObm1CMkpSRzN2RllCbmNjMDFsMVJsa3UyM2NhMmRlenVKck0ybjRJMFI0UA%3D%3D

As you can notice, it's slightly longer than your URL (especially it's ending with "%3D%3D"), thus my guess is it's truncated by SFDC developer console, or has some length limitation somewhere.

Duo

That was exactly the problem.  Thank you! I outputted the URL properly and it works great.

We like the option of using this method to input the URL into an email that Salesforce will send out because we can have it send as the Salesforce user rather than a generic system email from our company or from OneSpan.  However, we realize we are committed to managing the signing ceremony via Salesforce.  Which means we'll need to implement the event listener and then build logic to send our emails to the other signers in order and also the final email (plus reminders, a dashboard to track progress, custom objects for our transactions etc).  Is this a pattern you are seeing other Salesforce clients use?  Are there other implementation patterns we should consider?

åny thoughts on this pattern of sending all emails via Salesforce?

Hi Peter,

Not so sure about how other SFDC clients are handling with invitation emails, but besides sending emails with a generic system email from your company or from OneSpan, OneSpan does allow you to use a custom SMTP server, or to use DomainKeys Identified Mail (DKIM) signing with custom domain, which improves the email deliverability, and further builds a reputation on your domain over time. Please check the blog here:
https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-2

On the other side, if you decided to handle the activation/notify/reminder emails by your own SFDC integration, below blog series on how to register an OAuth client within Salesforce and listen to the OSS callback events might be helpful:
https://www.onespan.com/blog/onespan-sign-developers-oauth-event-notification-salesforce-part-1

https://www.onespan.com/blog/onespan-sign-developers-oauth-event-notification-salesforce-part-2

https://www.onespan.com/blog/onespan-sign-developers-oauth-event-notification-salesforce-part-3

Duo

Thank you!