Signature API

From Wikipedia, the free encyclopedia

Contents 1 SAPI - Signature API 2 SAPI & OASIS DSS (Digital Signature Services) 3 SAPI vs. other APIs 4 Signing Web forms and Web Applications with SAPI

[edit] SAPI - Signature API

SAPI - Signature API, developed by ARX, is a set of functions, protocols, and tools that programmers can use to enhance their applications with digital signatures.

Typical applications that benefit from digital signature support include: Workflow, Document Management, ERP, financial transactions (e.g., Fund Transfer), Laboratory Information Management Systems (LIMS), Engineering Change processes (ECO/ECN/ECR), Reporting, Archiving, Purchasing, Accounting (e.g., Invoicing, Billing, Auditing), Healthcare (e.g., patient consent forms), HR (e.g., reviews, expense report, time sheets), and applications that fall under various compliance requirements (e.g., SOX, HIPAA, FDA 21 CFR part 11).

With SAPI, application developers can easily integrate digital signatures into their application and eliminate the printing, handling, faxing, mailing and archiving of paper forms or policies.

[edit] SAPI & OASIS DSS (Digital Signature Services)

The OASIS DSS is the approved Web Services standard for digital signatures. This includes an interface for requesting that a web service produce and/or verify a digital signature on a given piece of data and techniques for proving that a signature was created within its key validity period.

The OASIS DSS specifications describe two XML-based request/response protocols – a signing protocol and a verifying protocol. Through these protocols a client can send documents to a server and receive back a signature on the documents; or send documents and a signature to a server, and receive back an answer on whether the signature verifies the documents. The DSS Core specifications provide the basic protocols and elements which are adapted to support specific use cases in the DSS profiles.

SAPI is the first commercial implementation of the OASIS DSS standard. More Info from OASIS's Website

[edit] SAPI vs. other APIs

Microsoft Cryptographic API (MS-CAPI) and PKCS#11 are two standard APIs that can be used to enhance an application with digital signature support, but SAPI offers a much simpler, more abstract, and more powerful approach. In addition to the simplicity, SAPI offers additional functionality such as support for Graphical Signatures; that is, the ability to add the graphical image of the hand-written signature into the application.

== SAPI Functionality Includes: Sign/Validate a signature in a supported application Sign/Validate a single file or data buffer Check certificate validity Batch sign multiple files (e-Invoices, e-Archiving, etc.) Enumerate/Manage certificates Add graphical signatures Manage users (Add, Delete, etc.)... and more …

[edit] Signing Web forms and Web Applications with SAPI

SAPI's support of Web signing ensures a convenient way for remote users to sign documents and data. With SAPIinto Web-signing solution, organizations can automate, expedite processes, and provide a much enhanced customer service. SAPI provides the means to add digital signature functionalities to any Web applications.

For example, an insurance company can use SAPI to have its clients electronically sign changes or updates to exiting policies without requiring printing and faxing of the updated policies back and forth between both parties. This process significantly minimizes the costs and time spent in printing, mailing or faxing paper policies. With CoSign’s SAPI the insurance company can easily add electronic signature functionalities to their Web application, and have their customers sign the transactions over the web. SAPI digital and graphical signatures ensures the accountability of the policy holder.