This trail describes how you can configure Openwings to authenticate
all components before installing them, and how you can build secure
components whose Jar files are checked on each run. This trail
assumes familiarity with basic Openwings security principles,
outlined in the Security
Introduction trail.
The remaining lessons in this trail are as follows:
- Configuring the Openwings core
- Creating a secure component image
- Adding additional "code signers" to the system
- Signing the individual Jars of your component
Next: Configuring
Security for the Openwings Install Service