By default, the Openwings Reference Implementation only knows
about its own code signers. If you wish to add keys for additional
code signers, you will need to do this using an administrative
tool such as keytool that comes with Java 2 Standard
Edition.
Documentation for keytool: Unix
| Windows
The file you will need to edit is denoted in the file ${OW_HOME}/openwings-1.0/policies/properties.txt
by the property com.gd.openwings.security.certstore
(Note that you could modify this property to point to a different
certificate store should you wish).
Here is an example command that will allow you to add your own
certificate to the certificate store, assuming a Windows install
with the default location (C:\openwings):
C:\openwings\openwings-1.0\system>keytool -import
-keystore owcerts -file mycert
Enter keystore password: ......
Once you have added a key to the owcerts file, you
can use jarsigner to sign the component or its contained
Jar files.
Note that keytool can be fairly cumbersome to use.
Here is a link
to a free GUI tool that has approximately the same functionality
(screenshots).
Next: Signing Libraries
