Overview
This documentation provides instructions for installing and using the OpenOTP Signature plugin for Windows OS.
To install and use the signature plugin, you need the following prerequisites:
- Deployed WebADM & OpenOTP server(s)
- OpenOTP Token mobile application
- Implemented push mechanisms
- A push token registered on the user account via the OpenOTP mobile application
- A license that includes the signature feature in OpenOTP
- Signature credits
Specific prerequisites for Windows machines include:
- .NET 6.0 Desktop Runtime installed
- Up-to-date Windows OS (compatible with Windows 10 version 2004 or later, from mid-2020)
The plugin facilitates electronic document/file signing directly from Windows machines, accessible by right-clicking on the document.
It supports all four types of signatures available in OpenOTP. For detailed information on these signature types, refer to the OpenOTP Signature documentation.
The person initiating the signature workflow is always the one performing the action; submitting a document for signature by someone else is not supported. For such needs, RCDevs offers other integrations, such as the Postfix mail server plugin.
After completing the signature workflow, the signed document is automatically retrieved from OpenOTP servers to the Windows machine. Both the original and signed files are stored at the same location, with the signed file name suffixed by "signed."
For the signature process to work, the OpenOTP SOAP API URLs must be accessible directly or via a reverse proxy (WAProxy). If the Windows machine cannot reach the OpenOTP backend, signing operations will not be possible.
Installation and configuration
Click on Install and after the installation you will be prompted to the configuration page.
Once on the configuration page, enter your WebADM server URL and click the Configure button. If WebADM server is reachable, OpenOTP service URLs should be automatically configured.
Else, manually provide your OpenOTP URL(s) in the corresponding fields as shown in the previous screenshot. Optionally, configure a client (recommended to enforce a signature mode for that client).
You also have the option to adjust the timeout for signature requests, and specify the Embedded Signature Suffix that will be added at the end of the newly signed document.
Click Ok once it is configured as desired.
Usage
Once the signature plugin for Windows is installed and properly configured, you can right-click on a document to submit it to OpenOTP for signature.
The document is sent to the OpenOTP backend, where OpenOTP prepares the transaction and sends it to the user's mobile device.
The user receives the signature request with the attached document. They can sign it and finalize the process. Once completed, the signed document will appear in the same location as the original, with a new suffix added to its name.
