peterzog

getSignerURL - Unauthorized Access

0 votes

I am using the APEX SDK to create a package, add a document and signers and then send. I receive an email to sign the document and it works great. 

Can I use getSignerURL to send the email from Salesforce as an alternative to sending the email from OneSpan servers? If so, what Is the best practice to prevent the standard email from being sent?

I tried running getSigningURL and got a link that looks legit but I get Unauthorized Access: Failed to validate token.  Is there a step I need to take prior?


Reply to: getSignerURL - Unauthorized Access

0 votes

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

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to:

0 votes

Reply to:

0 votes

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

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to:

0 votes

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?


Reply to:

0 votes

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

Duo Liang OneSpan Evangelism and Partner Integrations Developer


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