Missing signature required 2nd signer to sign

Hi Cindy,

Thanks for your post! Because it's Signer SSO + signers sharing the same email, it will take some time to set up a similar environment. Just a quick question that in your Active Directory, the recipients are having the same email and names as configured in the package (signer1 [email protected], Joan1 River1; signer2 [email protected], Joan2 River2), right?

Duo

This is only have in the remote eSig scenario, when the signer launch signing ceremony from email. 

Hi Cindy,

Do you by any chance have the package ID of this transaction? Want to check if signer1 has signed all the signatures, including the ones assigned for signer2.

Duo

Hi Duo, 

No, in AD, only 1 person setup, but the package is allow to use the same email for different signer, so we'd like to test it. 

Hi Cindy,

I see, that might be the case of issue. When signer logged in via SSO, the IDP will send first/last name and email to OneSpan Sign, which will be checked against the package JSON signer list to identify which signer is currently signing. Although the email can be shared across signers, but the name + email combination will still be the unique identification.

Duo

Hi Duo,

from the package signer list, signer1 and signer2 firstname and last name are all fake, only email address is correct and registered in our AD, in this case, how to identify? 

Hi Cindy,

From my understanding, I think it's a general rule that the name and email should be the same in both AD and package JSON. Mismatch information could result in errors during SAML authentication.

Duo

but in my case, the name is fake, and email is correct. the signer is able to launch the signing ceremony via email though. any idea?

Hi Duo, 

I found another scenario, it seems very odd. 

1) I created a package in my account ([email protected]), the package has 2 signers, both email is '[email protected]' which is the sender UI account in OSS, and I get 'error.validation.userAddition.duplicateEmailUsage' error, which is expected as

https://community.onespan.com/documentation/onespan-sign/guides/admin-guides/user/account-level-features

2) I created a package in my account ([email protected]), the package has 2 signers, both email is my account '[email protected]' , in this case, the package is successful created and sent, the only unexpected is there supposed to have 2 signers, now it became 1 signer. 

any idea for 2nd scenario? 

thanks,

Cindy

Hi Cindy,

I can reproduce the same that with the second scenario, instead of returning an error, the package was created unexpectedly. 

From my test, I believe this occurs when the duplicated email refers to the transaction sender (specifying sender with account owner's API Key also triggers this issue). I think it's more of an inconsistence that in this scenario, the API should also return the error like the first scenario does. If you preferred, we can report this to support and R&D team.

As a temporary workaround, you can add an additional check in your local that if the sender's email appears in multiple times, throw the duplicateEmailUsage error.

Duo