OneSpan Sign for Salesforce Error

Hi Josh,

Thanks for the post! As per your description, have you created an OneSpan Sign account then connect it to SFDC from the Admin tab, like the below screenshot indicates?

Duo

Duo,

Yes I have. But, the connected user is not myself. Even though I am an admin in OneSpan Sign, and an admin in Salesforce, whenever I try to connect myself I get an error telling me I need to connect with my managing user. So, I did that, but now whenever I try to prepare a transaction I get the error described above.

Thanks.

Hi Josh,

Did you install the Salesforce Connector with your email? That's because the person whom installed the connector should be both Salesforce Admin and the Onespan sign account owner.

If you can advise on the Salesforce admin email who installed the connector and the OneSpan Sign account email and environment, I can verify it for you. You can send these information to [email protected].

Duo

Hi Josh,

Thanks for the sharing! I saw you are connecting to OneSpan Sign sandbox environment, firstly please be aware that:
-Salesforce developer environment can only connect to OneSpan Sign production environment (https://apps.esignlive.com or https://apps.e-signlive.ca, etc)

-Salesforce sandbox environment can only connect to OneSpan Sign sandbox environment (https://sandbox.esignlive.com or https://sandbox.e-signlive.ca, etc)

That's to say, if you are not developing with a Salesforce sandbox environment, you won't be able to connect to https://sandbox.esignlive.com

Secondly, after checking with your account, your email josh.b***@m***.com is not the OneSpan Sign account owner or manager, so I guess it's expected that you can't connect with your own email. Choose one of the below two options to grant you enough permission:

-submit a support ticket at [email protected] and ask to switch your email as the account owner 

-or logged onto hd****@gmail.com's sender portal, navigate to "Admin" > "Senders" and assign your email as an account manager. In which case when connecting in SFDC, you'd use login credentials instead of the API Key.

Duo