question about locked signers and in-person signing
Monday, March 13, 2017 at 07:23amHi,
We've discovered some behaviour that seems strange/inconsistent to our team. It may just be a case of not understanding the APIs properly, but either way hopefully you can help us out.
Our application supports both remote and in-person signing. What we've discovered is that if we created a session token for in-person signing using a locked signer, then the resulting in-person ceremony is locked (just like if the signer were signing remotely).
However, if we create and open the ceremony using the sender as the owner of the session token then we can switch to the locked signer, and the locked signer is not locked.
This seems a little inconsistent to us. Should remote signers who are locked be able to participate in in-person signing ceremonies?
Here's the code we use to create the session token:
SessionToken sessionToken = eslClient.getSessionService().createSessionToken(docPackage.getId().getId(), signerId);
Thanks in advance,
-Chris
Reply to: question about locked signers and in-person signing
Monday, March 13, 2017 at 06:13pmReply to: question about locked signers and in-person signing
Tuesday, March 14, 2017 at 10:42amReply to: question about locked signers and in-person signing
Tuesday, March 14, 2017 at 11:15am