Server-Side and Client-Side Security Functions 

The following gives you information about the terms server-side and client-side, both used in connection with certification and signatures. Your application determines whether these security functions are used on the client side or on the server side. A signed document does not tell you whether it has been signed on the server side or on the client side. The same applies to certified documents. This information is not relevant for the further handling of a document, such as checking its certification or signature.

Server-Side

The application is always responsible for setting a server-side certification or a server-side signature. The process flow of this function, and also of other functions such as checks and user guidance, is determined by the programming of the application.

One example of an application with a server-side signature is an automated process in the SAP system for creating and sending (electronically) signed invoices. If you have a large number of invoices, it is a good idea to have a personalized (client-side) signature on each invoice, similar to mass printing for paper invoices.

Client-Side

Client-side indicates that you certify, sign, or check a form personally on your front end. To do this, you use Adobe Acrobat or Adobe Reader. Remember that you need Adobe Acrobat to certify a form. For more detailed information, see the online help of Adobe Acrobat and Adobe Reader. For many scenarios, it is sufficient just to implement client-side signatures.

You are filling out a purchase order form. The form already contains a signature field, created by the developer of the form. If you select this field, you can sign the filled out form. The dialog boxes in Adobe Acrobat or Adobe Reader help you to do this. 

For up-to-date information about the required Adobe Acrobat or Adobe Reader version, see SAP Note 834573.