Programmatically Lock a Signer

Hi Mitch, Unfortunately, there is no call available to programmatically lock a signer through the SDKs or API. A signer can only be locked if he/she unsuccessfully attempts too many times to answer Q&A/SMS authentication. What's your motivation behind locking a signer?

Hi Haris, So, does that also mean that neither SDKs or API can "unlock" a signer who has been locked out? Thanks, Todd

Hi Todd, Unlocking can be done through the SDKs/API: https://developer.esignlive.com/guides/feature-guides/unlocking-signers/ However, manually LOCKING a signer is not possible.

Thanks Haris.

Hi Haris, So, we continue to research some solutions to our REST API. Is there a means through the callback functionality, or any other event notification means, to identify the lock status for a signer? Thanks, Todd

There is an event "SIGNER_LOCKED" available that you can register with the callback notification functionality that will notify you if a signer failed SMS/Q&A authentication: http://docs.esignlive.com/content/c_integrator_s_guide/sdk/i_reports_and_logging/event_notifications.htm

Thanks Haris. Is there a setting somewhere else, or another means to determine why we're not getting a callback event through our API when a signer becomes locked? So, we found the "signer_locked" setting,. Then tested in in the Silanis Sandbox environment, and it works. That is we get a call through the API AND we get a signer locked email. Then we tested this setting within our on premise solution. We do get an email indicating the signer is locked. However we do not get notification for the callback event signer_locked when registered for that event with our callback url. This callbackurl listens to all events and creates a files with the event and package name. We successfully received event notification for document_signed, package_active,signer_complete event BUT NOT FOR SIGNER_LOCKED event. This test was run on a new transaction, used Q & A authentication for a signer, and we purposely lock them with three incorrect answer responses. Other callbacks are working such as document signed.

Hey Todd, You will need to send an email to [email protected] so they can investigate why the signer locked event is not working on your on-premise solution.

I did not mean to activate that -1 score. My apologies. I appreciate your timely responses, and I'll get a ticket open with support.

No worries :)