This trail describes how you can configure Openwings components
to have secure connectors. This trail assumes familiarity with
basic Openwings security principles, outlined in the Security
Introduction trail.
The main participants in Openwings Service and Transport security
are the Security Service and Secure connectors. Each half of an
Openwings secure connector authenticates to the Security Service
on the local platform. The secure connector provided in the reference
implementation is based on the Java
Generic Security Services (GSS) API introduced in Java 1.4.
Click above image to see full size
The Security Service participates in several aspects of security
authentication in Openwings:
- Authenticating service users – covered in this tutorial trail
- Management of users and roles on a platform – covered in the
Security
Introduction trail
- Code authentication - described in the Install Security Trail
The Security Service may be based on a federated identity solution
such as Liberty or Passport. However, the reference implementation
uses a separate Java keystore on each platform to contain users
and roles.
The remaining lessons in this trail are as follows:
- Running the secure HelloWorld demo
- Generating a secure connector
- Configuring your component to use the secure connector
Next: Running
the Secure HelloWorld Demo
