Enhancing PHP Applications with Digital Signatures Through SAPI Web Services

The CoSign@ digital signature solution enables users and applications to digitally sign documents and data through a Web Services interface called SAPI® Web Services. This Web-Services interface is based on OASIS Digital Signature Services (DSS) standard, which was announced in 2007 and is aimed at expanding application usage of digital signatures by setting definitions of how a digital signature application interacts with a centralized digital signature service (for more information, refer to www.oasisopen.org/committees/dss/ and www.oasis-open.org/committees/provision/).

One of the main benefits of SAPI Web Services is portability; there is a large variety of development environments and operating systems that can interact with it. In fact, any environment that supports SOAP (Simple Object Access Protocol) enhanced with TLS security, can benefit from using the digital signature capabilities of SAPI Web Services. Examples of such environments are Java-based applications that run on non-Windows platforms, pure .NET applications, and a variety of script languages such as PERL and PYTHON.

One of the leading script languages used extensively for Web application development is PHP. The PHP language has evolved greatly in recent years and it now enables Web developers to incorporate Web application login with minimal development efforts.

Since PHP includes SOAP capabilities and can also communicate securely with Web Services, it is simple to use CoSign from a PHP-based Web application through the SAPI Web Services interface. This document provides basic guidelines on how to use SAPI Web Services in a PHP environment, as well as a short coding sample.

Please note that in order to successfully use CoSign, you will need the Web Services description file (.wsdl) of SAPI Web Services. Also, note that the following example uses PEAR, which is a high-level PHP module that allows interaction with a Web Service.

The example shown on the right performs the following actions:

• Creating a PHP class enabling the building of a buffer request.
• Calling the DssSign operation for performing the signature operation.
• Getting a response from the digital signature service.
• Displaying the response to the user.