IBM WebSphere V5.0 Security - CGISecurity

Example 8-5 login.config
WSLogin {
com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy required
delegate=com.ibm.ws.security.common.auth.module.WSLoginModuleImpl;
};
The configuration file can have multiple definitions, each definition has an alias
name, which can be used in the application to set the login module. The entry
defines the Java class for the login module; the "required" means that this class's
approval is necessary for login to succeed. The entry can optionally define a
delegation class for the login module.
There can be a policy file for JAAS defined, similar to the policy files used in Java
2 security. Actually, the Java 2 Security and JAAS policy files may be merged in
the next release of Java, in J2EE V1.4. This policy file is optional.
Example 8-6 jaas.policy
grant Principal SamplePrincipal "user01" {
permission java.util.PropertyPermission
"user.home", "read";
};
The policy file defines the access policy for the resources in an application. The
policy defines the principal for the resources.
8.7 Programmatic login
When you want to implement your own login mechanism for your application, you
may want to use JAAS and implement the required programmatic login.
Figure 8-8 shows the activity diagram for JAAS and how the different
components are working together during a login process.
Chapter 8. Programmatic security 207