A smart card with proper keys is required to create the signatures in this example. The MIDlet must also be signed, since signing byte data is not allowed in an untrusted domain.
This example currently does not come with the certificate, so the user can not run it properly on the device or SDK. For information on how to acquire a certificate, see section Certificate acquisition.
This MIDlet generates signatures using the CMSMessageSignatureService
class.
The verification for these MIDlet-made signatures cannot be done in this same
MIDlet, since the signatures created by the CMSMessageSignatureService
class
are of CMS-format and the Signature-class verify()
method
doesn´t accept CMS-formatted signatures. Proper verification of signatures
should be performed, for example, through a server.
Note: Series 40 does not support the SATSA PKI package. Therefore this example cannot be run in Series 40.