CAYLX

LiquidOffice – Real, Digital Authentification

LiquidOffice provides LDAP authentication support for a range of built in digital approval options using HTML and PDF. Extended support includes digital signature standards incorporating PKI certificates and biometric signature devices from third party vendors for PDF forms, customers who require signing capabilities for low-risk transactions, including vacation requests, performance reviews, and engineering change orders.

LiquidOffice Digital Approval provides an excellent solution for digitally approving forms and their data without having to invest and maintain a system that uses a PKI certificate based system as the means for digitally signing documents.

LiquidOffice supports three levels of digital approval and signatures, and includes support for self authenticated and password/PIN protected digital form approval in HTML and PDF. LiquidOffice also supports certified PKI digital signature handlers.

Digital Approval provides a signature field and signing interface that authenticates a user based on their current login or it can require the user to re-enter their login id and password. Upon signing the document, the signature can lock all fields or just specified fields on the form. The signature information, which includes user and time stamp information, is contained within the form as it is routed from user to user, and upon final submission can also be exported along with the rest of the form data.

In cases where very sensitive data is being processed, a secure PKI certificate-based system can be implemented using a variety of third party signature plug-ins that work within Acrobat.

Digital Signature (PKI) Support

Powered by intuitive drag-and-drop technologies, LiquidOffice accelerates the design and execution of structured processes for unique business requirements and regulatory compliance needs. No programming expertise is required.

LiquidOffice also supports all certified Adobe Acrobat plug-in signature handlers from vendors such as Entrust, Verisign, and CIC.

Digital signature handlers determine the nature of the signatures, their appearance on the page, the exact information stored in them, and the attributes and method used for validation.

Paper Automation

One of the most powerful capabilities built into LiquidOffice is the ability to seamlessly capture paper forms and documents and connect them to processes that may already be active. In fact, LiquidOffice is the only integrated and unified solution that supports a single, consistent and auditable business process to be applied to both electronic and paper information streams. For users, this means they have the option of submitting paper forms or electronic forms. In situations where a wet signature is required or where federal or state government mandates require both options (paper and electronic forms) to be offered to consumers, this capability is critical.

Digital Signatures For Authentication

Although messages may often include information about the entity sending a message, that information may not be accurate. Digital signatures can be used to authenticate the source of messages. When ownership of a digital signature secret key is bound to a specific user, a valid signature shows that the message was sent by that user. The importance of high confidence in sender authenticity is especially obvious in a financial context. For example, suppose a bank's branch office sends instructions to the central office requesting a change in the balance of an account. If the central office is not convinced that such a message has truly been sent from an authorized source, acting on such a request could be a grave mistake.

Digital Signatures For Data Integrity

In many scenarios, the sender and receiver of a message may have a need for confidence that the message has not been altered during transmission. Although encryption hides the contents of a message, it may be possible to change an encrypted message without understanding it. However, if a message is digitally signed, any change in the message after signature will invalidate the signature. Furthermore, there is no efficient way to modify a message and its signature to produce a new message with a valid signature, because this is still considered to be computationally infeasible.