A number of examples demonstrate how to express various authentication
configuration requirements in subsystem instances in the authentication chain. They also
explain how the authentication chain integrates the functions of multiple subsystem instances
into a more powerful conglomerate, letting you cater for even the most complex authentication
scenarios.
These examples demonstrate the flexibility and power of an
authentication chain. You can combine the strengths of a variety of different authentication
protocols and keep the user database synchronized almost transparently.
The authentication configuration examples adopt the following structured approach:
- Decide the authentication chain composition (required subsystem types, instance names, order of precedence) and express this in the SkyVault-global.properties file.
- For each subsystem instance:
- Locate the properties files for its subsystem type. These properties files define the configurable properties for that subsystem type and their default values.
- Create a folder named after the subsystem instance under the extension folders.
- Copy the properties files into your new folder.
- Edit the properties files to record the required configuration of the subsystem instance.