Using Netscape signaturesAdded by IBM on October 10, 2012 | Version 1 (Original)
|The Netscape engine uses certificates located in the Netscape certificate store for signature security. Although the Viewer does not support Netscape, the Firefox browser also uses Netscape certificates.
To create a signature button that uses the Netscape engine, set the following parameters in the signformat option:
Netscape also uses an optional parameter to set the hash algorithm used to generate the signature. This parameter is:
- MIME type — The MIME type that will be used to store the signature information. You should always use application/vnd.xfdl.
- engine — The name of the signing engine to use. In this case, Netscape.
- delete — Optional. This flag sets whether the user can delete the signature. By default, users can delete all signatures. If you want to prevent a signature from being deleted, set this to off.
For example, the generic XFDL code for a button using the Netscape engine looks like this:
- hashalg — The name of the hash algorithm to use when generating the signature. Valid algorithms are sha1 and md5. The default algorithm is sha1.
- If the form is opened in Webform Server, then signing a Netscape signature requires the use of the Webform Server plugin/ActiveX control. The plugin/ActiveX control is automatically downloaded to the browser when it is needed.