The first step in using the secure version of Openwings is to
install the Openwings reference implementation. When installing
Openwings, the InstallAnywhere installer provides four options:
In the secure installations, the following core Openwings services
are configured to use secure connectors:
- Container Manager
- Container
- Installer
- Context
If a secure install option is chosen, access to these services
will be controlled via the Openwings Security Service.
Openwings comes with a single, default user, as described on
the next page. This user can be verified using the Openwings login
module. Openwings can also be configured to accept platform logins
by adding additional login modules.
The set of login modules used by Openwings is controlled by the
file ${OW_HOME}/openwings-1.0/system/owLogin.conf. On a Windows
NT install it looks like this:
openwings {
com.gd.openwings.security.login.OpenwingsLoginModule required
debug=false;
com.sun.security.auth.module.NTLoginModule optional debug=false;
};
This file setting configures Openwings to use the Openwings Login
Module and the Windows NT login module provided by Sun. For some
platforms, the InstallAnywhere installer attempts to do this automatically,
as shown below:
- Windows NT: com.sun.security.auth.module.NTLoginModule
- Solaris: com.sun.security.auth.module.SolarisLoginModule
(Currently, the Install Anywhere installer does not set the
NTLoginModule for Windows XP as this appears to cause a Java core
dump on Java 1.4.1_01 and _02.)
Next: Openwings
Login
